Method and apparatus for obtaining time alignment regarding multiple trps in a wireless communication system

ABSTRACT

Methods, systems, and apparatuses are provided for enhancing timing alignment for uplink (UL) multi-Transmission/Reception Point (TRP) (or mTRP) scenarios in a wireless communication system. A method for a UE in a wireless communication system can comprise receiving a signaling, wherein the signaling indicates activation for a first TRP and/or is a Physical Downlink Control Channel (PDCCH) signal, determining to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first Time Alignment (TA) information associated with the first TRP, and performing multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present Application claims priority to and the benefit of U.S. Provisional Pat. Application Serial No. 63/226,155, filed Jul. 27, 2021, U.S. Provisional Pat. Application Serial No. 63/226,161, filed Jul. 27, 2021, and U.S. Provisional Pat. Application Serial No. 63/231,545, filed Aug. 10, 2021; with each of the referenced applications and disclosures fully incorporated herein by reference.

FIELD

This disclosure generally relates to wireless communication networks and, more particularly, to a method and apparatus for enhancing timing alignment for uplink (UL) multi-Transmission/Reception Point (TRP) (or mTRP) scenarios in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communication can provide users of mobile communication devices with voice over IP, multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput in order to realize the above-noted voice over IP and multimedia services. A new radio technology for the next generation (e.g., 5G) is currently being discussed by the 3GPP standards organization. Accordingly, changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.

SUMMARY

Methods, systems, and apparatuses are provided for enhancing timing alignment for uplink (UL) multi-Transmission/Reception Point (TRP) (or mTRP) scenarios in a wireless communication system.

In various embodiments, with this and other concepts, systems, and methods of the present invention, a method for a UE in a wireless communication system comprises receiving a signaling, wherein the signaling indicates activation for a first Transmission/Reception Point (TRP) and/or is a Physical Downlink Control Channel (PDCCH) signal, determining to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first Time Alignment (TA) information associated with the first TRP, and performing multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system, in accordance with embodiments of the present invention.

FIG. 2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE), in accordance with embodiments of the present invention.

FIG. 3 is a functional block diagram of a communication system, in accordance with embodiments of the present invention.

FIG. 4 is a functional block diagram of the program code of FIG. 3 , in accordance with embodiments of the present invention.

FIG. 5 is a reproduction of Figure 6.1.3.4-1 of 3GPP TS 38.321, V16.5.0: Timing Advance Command MAC CE.

FIG. 6 is a reproduction of Figure 6.1.3.4a-1 of 3GPP TS 38.321, V16.5.0: Absolute Timing Advance Command MAC CE.

FIG. 7 is a reproduction of Figure 6.1.3.15-1 of 3GPP TS 38.321, V16.5.0: TCI State Indication for UE-specific PDCCH MAC CE.

FIG. 8 is a reproduction of Figure 6.1.3.14-1 of 3GPP TS 38.321, V16.5.0: TCI States Activation/Deactivation for UE-specific PDSCH MAC CE.

FIG. 9 is a reproduction of Figure 6.1.3.24-1 of 3GPP TS 38.321, V16.5.0: Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE.

FIG. 10 is a reproduction of Figure 6.1.3.25-1 of 3GPP TS 38.321, V16.5.0: Enhanced PUCCH spatial relation Activation/Deactivation MAC CE.

FIG. 11 is a reproduction of Figure 6.1.3.26-1 of 3GPP TS 38.321, V16.5.0: Enhanced SP/AP SRS spatial relation Indication MAC CE.

FIG. 12 is a reproduction of Figure 4.3.1-1 of 3GPP TS 38.211, V16.6.0: Uplink-downlink timing relation.

FIG. 13 is an example of an extended TAC MAC CE, in accordance with embodiments of the present invention.

FIGS. 14A and 14B are examples of an extended TAC MAC CE for a non-serving cell, in accordance with embodiments of the present invention.

FIG. 15A is another example of an extended TAC MAC CE, in accordance with embodiments of the present invention.

FIG. 15B is an example wherein a MAC CE could contain a non-serving cell ID and a UE applies the Offset1 or TAC_TRP2 to the non-serving cell associated with Non-serving cell id1, in accordance with embodiments of the present invention.

FIG. 15C is an example wherein a MAC CE could contain more than one offset or TAC for non-serving cells, in accordance with embodiments of the present invention.

FIG. 15D is another example wherein a MAC CE could contain more than one offset or TAC for non-serving cells, in accordance with embodiments of the present invention.

FIG. 16 is a flow diagram of a method of a UE receiving, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP, in accordance with embodiments of the present invention.

FIG. 17 is a flow diagram of a method of a UE performing UL transmission on a first TRP and a second TRP, in accordance with embodiments of the present invention.

FIG. 18 is a flow diagram of a method of a UE performing inter-cell mTRP operation on a serving cell and a non-serving cell, in accordance with embodiments of the present invention.

FIG. 19 is a flow diagram of a method of a network configuring a UE with UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP, in accordance with embodiments of the present invention.

FIG. 20 is a flow diagram of a method of a UE receiving, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated a second TRP, in accordance with embodiments of the present invention.

FIG. 21 is a flow diagram of a method of a UE receiving a signaling, wherein the signaling indicates activation for a first TRP and/or is a PDCCH signal, in accordance with embodiments of the present invention.

DETAILED DESCRIPTION

The invention described herein can be applied to or implemented in exemplary wireless communication systems and devices described below. In addition, the invention is described mainly in the context of the 3GPP architecture reference model. However, it is understood that with the disclosed information, one skilled in the art could easily adapt for use and implement aspects of the invention in a 3GPP2 network architecture as well as in other network architectures.

The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A (Long Term Evolution Advanced) wireless access, 3GPP2 UMB (Ultra Mobile Broadband), WiMax, 3GPP NR (New Radio), or some other modulation techniques.

In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including: [1] RP-193133 New WID: Further enhancements on MIMO for NR; [2] 3GPP TS 38.213, V16.6.0; [3] 3GPP TS 38.321, V16.5.0; [4] 3GPP TS 38.331, v16.5.0; [5] 3GPP TS 38.211, V16.6.0; and [6] 3GPP TS 38.212, V16.6.0. The standards and documents listed above are hereby expressly and fully incorporated herein by reference in their entirety.

FIG. 1 shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In FIG. 1 , only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal (AT) 116 is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from AT 116 over reverse link 118. AT 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 over forward link 126 and receive information from AT 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency than that used by reverse link 118.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, antenna groups each are designed to communicate to access terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmitting antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage normally causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

The AN may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an eNodeB, or some other terminology. The AT may also be called User Equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 220 then provides N_(T) modulation symbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. N_(T) modulated signals from transmitters 222 a through 222 t are then transmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are received by N_(R) antennas 252 a through 252 r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254 a through 254 r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) received symbol streams from N_(R) receivers 254 based on a particular receiver processing technique to provide N_(T) “detected” symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250. Processor 230 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Memory 232 may be used to temporarily store some buffered/computational data from 240 or 242 through Processor 230, store some buffed data from 212, or store some specific program codes. And Memory 272 may be used to temporarily store some buffered/computational data from 260 through Processor 270, store some buffed data from 236, or store some specific program codes.

Turning to FIG. 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention. As shown in FIG. 3 , the communication device 300 in a wireless communication system can be utilized for realizing the UEs (or ATs) 116 and 122 in FIG. 1 , and the wireless communications system is preferably the NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling an operation of the communications device 300. The communications device 300 can receive signals input by a user through the input device 302, such as a keyboard or keypad, and can output images and sounds through the output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, delivering received signals to the control circuit 306, and outputting signals generated by the control circuit 306 wirelessly.

FIG. 4 is a simplified block diagram of the program code 312 shown in FIG. 3 in accordance with an embodiment of the invention. In this embodiment, the program code 312 includes an application layer 400, a Layer 3 portion 402, and a Layer 2 portion 404, and is coupled to a Layer 1 portion 406. The Layer 3 portion 402 generally performs radio resource control. The Layer 2 portion 404 generally performs link control. The Layer 1 portion 406 generally performs physical connections.

For LTE, LTE-A, or NR systems, the Layer 2 portion 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The Layer 3 portion 402 may include a Radio Resource Control (RRC) layer.

Any two or more than two of the following paragraphs, (sub-)bullets, points, actions, or claims described in each invention paragraph or section may be combined logically, reasonably, and properly to form a specific method.

Any sentence, paragraph, (sub-)bullet, point, action, or claim described in each of the following invention paragraphs or sections may be implemented independently and separately to form a specific method or apparatus. Dependency, e.g., “based on”, “more specifically”, “example”, etc., in the following invention disclosure is just one possible embodiment which would not restrict the specific method or apparatus.

In Work item description for Further enhancements on MIMO for NR ([1] RP-193133 New WID: Further enhancements on MIMO for NR), beam management considering multi-TRP/panel operation, is considered as one of the objectives:

3 Justification

The Rel-15 NR includes a number of MIMO features that facilitate utilization of a large number of antenna elements at base station for both sub-6GHz and over-6GHz frequency bands. The Rel-16 NR enhances Rel-15 by introducing enhanced Type II codebook with DFT-based compression, support for multi-TRP transmission especially for eMBB and PDSCH, enhancements for multi-beam operation including reduction in latency and/or overhead for various reconfigurations (QCL-related, measurements), SCell beam failure recovery (BFR), and L1-SINR. In addition, low PAPR reference signals and features enabling uplink full-power transmission are also introduced.

As NR is in the process of commercialization, various aspects that require further enhancements can be identified from real deployment scenarios. Such aspects include the following. First, while Rel-16 manages to offer some reduction in overhead and/or latency, high-speed vehicular scenarios (e.g. a UE traveling at high speed on highways) at FR2 require more aggressive reduction in latency and overhead - not only for intra-cell, but also for L1/L2 centric inter-cell mobility. This also includes reducing the occurrence of beam failure events. Second, while enhancements for enabling panel-specific UL beam selection was investigated in Rel-16, there was not sufficient time to complete the work. This offers some potential for increasing UL coverage including, e.g. mitigating the UL coverage loss due to meeting the MPE (maximum permissible exposure) regulation. It is noted that MPE issue may occur on all transmit beams from the panel, therefore, a solution for MPE mitigation may only be performed per panel basis to meet the regulatory requirement for scenarios of interest.

Third, channels other than PDSCH can benefit from multi-TRP transmission (as well as multi-panel reception) which also includes multi-TRP for inter-cell operations. This includes some new use cases for multi-TRP such as UL dense deployment within a macro-cell and/or heterogeneous-network-type deployment scenarios. Fourth, due to the use of SRS for various scenarios, SRS can and should be further enhanced at least for capacity and coverage. Fifth, although Rel-16 supports enhanced Type II CSI, some room for further enhancements can be perceived. This includes CSI designed for multi-TRP/panel for NC-JT use case and the utilization of partial reciprocity on channel statistics such as angle(s) and delay(s) mainly targeting FR1 FDD deployments.

4 Objective 4.1 Objective of SI or Core Part WI or Testing Part WI

The work item aims to specify the further enhancements identified for NR MIMO. The detailed objectives are as follows:

-   Extend specification support in the following areas [RAN1]     -   1. Enhancement on multi-beam operation, mainly targeting FR2         while also applicable to FR1:         -   a. Identify and specify features to facilitate more             efficient (lower latency and overhead) DL/UL beam management             to support higher intra- and Ll/L2-centric inter-cell             mobility and/or a larger number of configured TCI states:             -   i. Common beam for data and control                 transmission/reception for DL and UL, especially for                 intra-band CA             -   ii. Unified TCI framework for DL and UL beam indication             -   iii. Enhancement on signaling mechanisms for the above                 features to improve latency and efficiency with more                 usage of dynamic control signaling (as opposed to RRC)         -   b. Identify and specify features to facilitate UL beam             selection for UEs equipped with multiple panels, considering             UL coverage loss mitigation due to MPE, based on UL beam             indication with the unified TCI framework for UL fast panel             selection     -   2. Enhancement on the support for multi-TRP deployment,         targeting both FR1 and FR2:         -   a. Identify and specify features to improve reliability and             robustness for channels other than PDSCH (that is, PDCCH,             PUSCH, and PUCCH) using multi-TRP and/or multi-panel, with             Rel 0.16 reliability features as the baseline         -   b. Identify and specify QCL/TCI-related enhancements to             enable inter-cell multi-TRP operations, assuming multi-DCI             based multi-PDSCH reception         -   c. Evaluate and, if needed, specify beam-management-related             enhancements for simultaneous multi-TRP transmission with             multi-panel reception     -   In 3GPP specification 38.213[2], timing adjustment for UL         transmisison is introduced:

4.2 Transmission Timing Adjustments

A UE can be provided a value N_(TA,offset) of a timing advance offset for a serving cell by n-TimingAdvanceOffset for the serving cell. If the UE is not provided n-TimingAdvanceOffset for a serving cell, the UE determines a default value N_(TA),_(offset) of the timing advance offset for the serving cell as described in [10, TS 38.133].

If a UE is configured with two UL carriers for a serving cell, a same timing advance offset value N_(TA),_(offset) applies to both carriers.

Upon reception of a timing advance command for a TAG, the UE adjusts uplink timing for PUSCH/SRS/PUCCH transmission on all the serving cells in the TAG based on a value N_(TA), _(offset) that the UE expects to be same for all the serving cells in the TAG and based on the received timing advance command where the uplink timing for PUSCH/SRS/PUCCH transmissions is the same for all the serving cells in the TAG.

A timing advance command [11, TS 38.321] in case of random access response or in an absolute timing advance command MAC CE, T_(A), for a TAG indicates N_(TA) values by index values of T_(A) = 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2^(µ)·15 kHz is N_(TA) = T_(A) ·16· 64/2^(µ). N_(TA) is defined in [4, TS 38.211] and is relative to the SCS of the first uplink transmission from the UE after the reception of the random access response or absolute timing advance command MAC CE.

In other cases, a timing advance command [11, TS 38.321], T_(A), for a TAG indicates adjustment of a current N_(TA) value, N_(TA_old), to the new N_(TA) value, N_(TA_new,) by index values of T_(A) = 0, 1, 2,..., 63, where for a SCS of 2^(µ) ·15 kHz, N_(TA_) _(new) = N_(TA_) _(old) +(T_(A)-31)·16·64/2^(µ) .

Adjustment of an N_(TA) value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing for the TAG by a corresponding amount, respectively.

If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command as described in [10, TS 38.133], the UE changes N_(TA) accordingly.

In 3GPP specification 38.321[3], random access procedure and TA maintenance are introduced:

5.1 Random Access Procedure 5.1.1 Random Access Procedure Initialization

The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by RRC for the events in accordance with TS 38.300 [2]. There is only one Random Access procedure ongoing at any point in time in a MAC entity. The Random Access procedure on an SCell shall only be initiated by a PDCCH order with ra-PreambleIndex different from 0b000000.

5.1.3 Random Access Preamble Transmission

The MAC entity shall, for each Random Access Preamble:

-   1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one; and -   1> if the notification of suspending power ramping counter has not     been received from lower layers; and -   1> if LBT failure indication was not received from lower layers for     the last Random Access Preamble transmission; and -   1> if SSB or CSI-RS selected is not changed from the selection in     the last Random Access Preamble transmission:     -   2> increment PREAMBLE_POWER_RAMPING_COUNTER by 1. -   1> select the value of DELTA_PREAMBLE according to clause 7.3; -   1> set PREAMBLE_RECEIVED_TARGET_POWER to     preambleReceivedTargetPower + DELTA_PREAMBLE +     (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP +     POWER_OFFSET_2STEP_RA; -   1> except for contention-free Random Access Preamble for beam     failure recovery request, compute the RA-RNTI associated with the     PRACH occasion in which the Random Access Preamble is transmitted; -   1> instruct the physical layer to transmit the Random Access     Preamble using the selected PRACH occasion, corresponding RA-RNTI     (if available), PREAMBLE_INDEX, and PREAMBLE_RECEIVED_TARGET_POWER.

5.1.3a MSGA Transmission

The MAC entity shall, for each MSGA:

-   1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one; and -   1> if the notification of suspending power ramping counter has not     been received from lower layers; and -   1> if LBT failure indication was not received from lower layers for     the last MSGA Random Access Preamble transmission; and -   1> if SSB selected is not changed from the selection in the last     Random Access Preamble transmission:     -   2> increment PREAMBLE_POWER_RAMPING_COUNTER by 1. -   1> select the value of DELTA_PREAMBLE according to clause 7.3; -   1> set PREAMBLE_RECEIVED_TARGET_POWER to     msgA-PreambleReceivedTargetPower + DELTA_PREAMBLE +     (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP; -   1> if this is the first MSGA transmission within this Random Access     procedure:     -   2> if the transmission is not being made for the CCCH logical         channel:         -   3> indicate to the Multiplexing and assembly entity to             include a C-RNTI MAC CE in the subsequent uplink             transmission.     -   2> if the Random Access procedure was initiated for SpCell beam         failure recovery and spCell-BFR-CBRA with value true is         configured:         -   3> indicate to the Multiplexing and assembly entity to             include a BFR MAC CE or a Truncated BFR MAC CE in the             subsequent uplink transmission.     -   2> obtain the MAC PDU to transmit from the Multiplexing and         assembly entity according to the HARQ information determined for         the MSGA payload (see clause 5.1.2a) and store it in the MSGA         buffer. -   1> compute the MSGB-RNTI associated with the PRACH occasion in which     the Random Access Preamble is transmitted; -   1> instruct the physical layer to transmit the MSGA using the     selected PRACH occasion and the associated PUSCH resource of MSGA     (if the selected preamble and PRACH occasion is mapped to a valid     PUSCH occasion), using the corresponding RA-RNTI, MSGB-RNTI,     PREAMBLE_INDEX, PREAMBLE_RECEIVED_TARGET_POWER,     msgA-PreambleReceivedTargetPower, and the amount of power ramping     applied to the latest MSGA preamble transmission (i.e.     (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP);

5.1.4 Random Access Response Reception

Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the MAC entity shall:

-   1> if the contention-free Random Access Preamble for beam failure     recovery request was transmitted by the MAC entity:     -   2> start the ra-Response Window configured in         BeamFailureRecoveryConfig at the first PDCCH occasion as         specified in TS 38.213 [6] from the end of the Random Access         Preamble transmission;     -   2> monitor for a PDCCH transmission on the search space         indicated by recoverySearchSpaceld of the SpCell identified by         the C-RNTI while ra-ResponseWindow is running. -   1> else:     -   2> start the ra-ResponseWindow configured in RACH-ConfigCommon         at the first PDCCH occasion as specified in TS 38.213 [6] from         the end of the Random Access Preamble transmission;     -   2> monitor the PDCCH of the SpCell for Random Access Response(s)         identified by the RA-RNTI while the ra-ResponseWindow is         running. -   1> if notification of a reception of a PDCCH transmission on the     search space indicated by recoverySearchSpaceId is received from     lower layers on the Serving Cell where the preamble was transmitted;     and -   1> if PDCCH transmission is addressed to the C-RNTI; and -   1> if the contention-free Random Access Preamble for beam failure     recovery request was transmitted by the MAC entity:     -   2> consider the Random Access procedure successfully completed. -   1> else if a valid (as specified in TS 38.213 [6]) downlink     assignment has been received on the PDCCH for the RA-RNTI and the     received TB is successfully decoded:     -   2> if the Random Access Response contains a MAC subPDU with         Backoff Indicator:         -   3> set the PREAMBLE_BACKOFF to value of the BI field of the             MAC subPDU using Table 7.2-1, multiplied with             SCALING_FACTOR_Bl.     -   2> else:         -   3> set the PREAMBLE_BACKOFF to 0 ms.     -   2> if the Random Access Response contains a MAC subPDU with         Random Access Preamble identifier corresponding to the         transmitted PREAMBLE_INDEX (see clause 5.1.3):         -   3> consider this Random Access Response reception             successful.     -   2> if the Random Access Response reception is considered         successful:         -   3> if the Random Access Response includes a MAC subPDU with             RAPID only:             -   4> consider this Random Access procedure successfully                 completed;             -   4> indicate the reception of an acknowledgement for SI                 request to upper layers.         -   3> else:             -   4> apply the following actions for the Serving Cell                 where the Random Access Preamble was transmitted:             -   5> process the received Timing Advance Command (see                 clause 5.2);             -   5> indicate the preambleReceivedTargetPower and the                 amount of power ramping applied to the latest Random                 Access Preamble transmission to lower layers (i.e.                 (PREAMBLE_POWER_RAMPING_COUNTER - 1) ×                 PREAMBLE_POWER_RAMPING_STEP);             -   5> if the Random Access procedure for an SCell is                 performed on uplink carrier where pusch-Config is not                 configured:             -   6> ignore the received UL grant.             -   5> else:             -   6> process the received UL grant value and indicate it                 to the lower layers.

            -   4> if the Random Access Preamble was not selected by the                 MAC entity among the contention-based Random Access                 Preamble(s):             -   5> consider the Random Access procedure successfully                 completed.

            -   4> else:             -   5> set the TEMPORARY_C-RNTI to the value received in the                 Random Access Response;             -   5> if this is the first successfully received Random                 Access Response within this Random Access procedure:             -   6> if the transmission is not being made for the CCCH                 logical channel:             -   7> indicate to the Multiplexing and assembly entity to                 include a C-RNTI MAC CE in the subsequent uplink                 transmission.             -   6> if the Random Access procedure was initiated for                 SpCell beam failure recovery and spCell-BFR-CBRA with                 value true is configured:             -   7> indicate to the Multiplexing and assembly entity to                 include a BFR MAC CE or a Truncated BFR MAC CE in the                 subsequent uplink transmission.             -   6> obtain the MAC PDU to transmit from the Multiplexing                 and assembly entity and store it in the Msg3 buffer.

5.1.4a MSGB Reception and Contention Resolution for 2-Step RA Type

Once the MSGA preamble is transmitted, regardless of the possible occurrence of a measurement gap, the MAC entity shall:

-   1> start the msgB-ResponseWindow at the PDCCH occasion as specified     in TS 38.213 [6], clause 8.2A; -   1> monitor the PDCCH of the SpCell for a Random Access Response     identified by MSGB-RNTI while the msgB-ResponseWindow is running; -   1> if C-RNTI MAC CE was included in the MSGA:     -   2> monitor the PDCCH of the SpCell for Random Access Response         identified by the C-RNTI while the msgB-ResponseWindow is         running. -   1> if notification of a reception of a PDCCH transmission of the     SpCell is received from lower layers:     -   2> if the C-RNTI MAC CE was included in MSGA:         -   3> if the Random Access procedure was initiated for SpCell             beam failure recovery (as specified in clause 5.17) and the             PDCCH transmission is addressed to the C-RNTI:             -   4> consider this Random Access Response reception                 successful;             -   4> stop the msgB-ResponseWindow;             -   4> consider this Random Access procedure successfully                 completed.         -   3> else if the timeAlignmentTimer associated with the PTAG             is running:             -   4> if the PDCCH transmission is addressed to the C-RNTI                 and contains a UL grant for a new transmission:             -   5> consider this Random Access Response reception                 successful;             -   5> stop the msgB-ResponseWindow;             -   5> consider this Random Access procedure successfully                 completed.         -   3> else:             -   4> if a downlink assignment has been received on the                 PDCCH for the C-RNTI and the received TB is successfully                 decoded:             -   5> if the MAC PDU contains the Absolute Timing Advance                 Command MAC CE:             -   6> process the received Timing Advance Command (see                 clause 5.2);             -   6> consider this Random Access Response reception                 successful;             -   6> stop the msgB-ResponseWindow;             -   6> consider this Random Access procedure successfully                 completed and finish the disassembly and demultiplexing                 of the MAC PDU.

    -   2> if a valid (as specified in TS 38.213 [6]) downlink         assignment has been received on the PDCCH for the MSGB-RNTI and         the received TB is successfully decoded:         -   3> if the MSGB contains a MAC subPDU with Backoff Indicator:             -   4> set the PREAMBLE_BACKOFF to value of the BI field of                 the MAC subPDU using Table 7.2-1, multiplied with                 SCALING_FACTOR_BI.         -   3> else:             -   4> set the PREAMBLE_BACKOFF to 0 ms.         -   3> if the MSGB contains a fallbackRAR MAC subPDU; and         -   3> if the Random Access Preamble identifier in the MAC             subPDU matches the transmitted PREAMBLE_INDEX (see clause             5.1.3a):             -   4> consider this Random Access Response reception                 successful;             -   4> apply the following actions for the SpCell:             -   5> process the received Timing Advance Command (see                 clause 5.2);             -   5> indicate the msgA-PreambleReceivedTargetPower and the                 amount of power ramping applied to the latest Random                 Access Preamble transmission to lower layers (i.e.                 (PREAMBLE_POWER_RAMPING_COUNTER - 1) ×                 PREAMBLE_POWER_RAMPING_STEP);             -   5> if the Random Access Preamble was not selected by the                 MAC entity among the contention-based Random Access                 Preamble(s):             -   6> consider the Random Access procedure successfully                 completed;             -   6> process the received UL grant value and indicate it                 to the lower layers.             -   5> else:             -   6> set the TEMPORARY_C-RNTI to the value received in the                 Random Access Response;             -   6> if the Msg3 buffer is empty:             -   7> obtain the MAC PDU to transmit from the MSGA buffer                 and store it in the Msg3 buffer;             -   6> process the received UL grant value and indicate it                 to the lower layers and proceed with Msg3 transmission.         -   3> else if the MSGB contains a successRAR MAC subPDU; and         -   3> if the CCCH SDU was included in the MSGA and the UE             Contention Resolution Identity in the MAC subPDU matches the             CCCH SDU:             -   4> stop msgB-Response Window;             -   4> if this Random Access procedure was initiated for                 SIrequest:             -   5> indicate the reception of an acknowledgement for                 SIrequest to upper layers.             -   4> else:             -   5> set the C-RNTI to the value received in the                 successRAR;             -   5> apply the following actions for the SpCell:             -   6> process the received Timing Advance Command (see                 clause 5.2);             -   6> indicate the msgA-PreambleReceivedTargetPower and the                 amount of power ramping applied to the latest Random                 Access Preamble transmission to lower layers (i.e.                 (PREAMBLE_POWER_RAMPING_COUNTER - 1) ×                 PREAMBLE_POWER_RAMPING_STEP).             -   4> deliver the TPC, PUCCH resource Indicator,                 ChannelAccess-CPext (if indicated), and HARQfeedback                 Timing Indicator received in successRAR to lower layers.             -   4> consider this Random Access Response reception                 successful;             -   4> consider this Random Access procedure successfully                 completed;             -   4> finish the disassembly and demultiplexing of the MAC                 PDU.

5.1.5Contention Resolution

Once Msg3 is transmitted the MAC entity shall:

-   1> start the ra-ContentionResolutionTimer and restart the     ra-ContentionResolutionTimer at each HARQ retransmission in the     first symbol after the end of the Msg3 transmission; -   1> monitor the PDCCH while the ra-ContentionResolutionTimer is     running regardless of the possible occurrence of a measurement gap; -   1> if notification of a reception of a PDCCH transmission of the     SpCell is received from lower layers:     -   2> if the C-RNTI MAC CE was included in Msg3:         -   3> if the Random Access procedure was initiated for SpCell             beam failure recovery (as specified in clause 5.17) and the             PDCCH transmission is addressed to the C-RNTI; or         -   3> if the Random Access procedure was initiated by a PDCCH             order and the PDCCH transmission is addressed to the C-RNTI;             or         -   3> if the Random Access procedure was initiated by the MAC             sublayer itself or by the RRC sublayer and the PDCCH             transmission is addressed to the C-RNTI and contains a UL             grant for a new transmission:             -   4> consider this Contention Resolution successful;             -   4> stop ra-ContentionResolutionTimer;             -   4> discard the TEMPORARY_C-RNTI;             -   4> consider this Random Access procedure successfully                 completed.     -   2> else if the CCCH SDU was included in Msg3 and the PDCCH         transmission is addressed to its TEMPORARY_C-RNTI:         -   3> if the MAC PDU is successfully decoded:             -   4> stop ra-ContentionResolutionTimer;             -   4> if the MAC PDU contains a UE Contention Resolution                 Identity MAC CE; and             -   4> if the UE Contention Resolution Identity in the MAC                 CE matches the CCCH SDU transmitted in Msg3:             -   5> consider this Contention Resolution successful and                 finish the disassembly and demultiplexing of the MAC                 PDU;             -   5> if this Random Access procedure was initiated for SI                 request:             -   6> indicate the reception of an acknowledgement for SI                 request to upper layers.             -   5> else:             -   6> set the C-RNTI to the value of the TEMPORARY_C-RNTI;             -   5> discard the TEMPORARY_C-RNTI;             -   5> consider this Random Access procedure successfully                 completed.             -   4> else:             -   5> discard the TEMPORARY_C-RNTI;             -   5> consider this Contention Resolution not successful                 and discard the successfully decoded MAC PDU.

5.2 Maintenance of Uplink Time Alignment

RRC configures the following parameters for the maintenance of UL time alignment: timeAlignmentTimer (per TAG) which controls how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned.

The MAC entity shall:

-   1> when a Timing Advance Command MAC CE is received, and if an     N_(TA) (as defined in TS 38.211 [8]) has been maintained with the     indicated TAG:     -   2> apply the Timing Advance Command for the indicated TAG;     -   2> start or restart the timeAlignmentTimer associated with the         indicated TAG. -   1> when a Timing Advance Command is received in a Random Access     Response message for a Serving Cell belonging to a TAG or in a MSGB     for an SpCell:     -   2> if the Random Access Preamble was not selected by the MAC         entity among the contention-based Random Access Preamble:         -   3> apply the Timing Advance Command for this TAG;         -   3> start or restart the timeAlignmentTimer associated with             this TAG.     -   2> else if the timeAlignmentTimer associated with this TAG is         not running:         -   3> apply the Timing Advance Command for this TAG;         -   3> start the timeAlignmentTimer associated with this TAG;         -   3> when the Contention Resolution is considered not             successful as described in clause 5.1.5; or         -   3> when the Contention Resolution is considered successful             for SI request as described in clause 5.1.5, after             transmitting HARQ feedback for MAC PDU including UE             Contention Resolution Identity MAC CE:             -   4> stop timeAlignmentTimer associated with this TAG.     -   2> else:         -   3> ignore the received Timing Advance Command. -   1> when an Absolute Timing Advance Command is received in response     to a MSGA transmission including C-RNTI MAC CE as specified in     clause 5.1.4a:     -   2> apply the Timing Advance Command for PTAG;     -   2> start or restart the timeAlignmentTimer associated with PTAG. -   1> when a timeAlignmentTimer expires:     -   2> if the timeAlignmentTimer is associated with the PTAG:         -   3> flush all HARQ buffers for all Serving Cells;         -   3> notify RRC to release PUCCH for all Serving Cells, if             configured;         -   3> notify RRC to release SRS for all Serving Cells, if             configured;         -   3> clear any configured downlink assignments and configured             uplink grants;         -   3> clear any PUSCH resource for semi-persistent CSI             reporting;         -   3> consider all running timeAlignmentTimers as expired;         -   3> maintain N_(TA) (defined in TS 38.211 [8]) of all TAGs.     -   2> else if the timeAlignmentTimer is associated with an STAG,         then for all Serving Cells belonging to this TAG:         -   3> flush all HARQ buffers;         -   3> notify RRC to release PUCCH, if configured;         -   3> notify RRC to release SRS, if configured;         -   3> clear any configured downlink assignments and configured             uplink grants;         -   3> clear any PUSCH resource for semi-persistent CSI             reporting;         -   3> maintain N_(TA) (defined in TS 38.211 [8]) of this TAG.

When the MAC entity stops uplink transmissions for an SCell due to the fact that the maximum uplink transmission timing difference between TAGs of the MAC entity or the maximum uplink transmission timing difference between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the timeAlignmentTimer associated with the SCell as expired.

The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble and MSGA transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running. Furthermore, when the timeAlignmentTimer associated with the PTAG is not running, the MAC entity shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble and MSGA transmission on the SpCell.

6.1.3.4Timing Advance Command MAC CE

The Timing Advance Command MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.4-1):

-   TAG Identity (TAG ID): This field indicates the TAG Identity of the     addressed TAG. The TAG containing the SpCell has the TAG Identity 0.     The length of the field is 2 bits; -   Timing Advance Command: This field indicates the index value T_(A)     (0, 1, 2... 63) used to control the amount of timing adjustment that     MAC entity has to apply (as specified in TS 38.213 ). The length of     the field is 6 bits.

FIG. 5 Is a Reproduction of Figure 6.1.3.4-1 of 3GPP TS 38.321, V16.5.0: Timing Advance Command MAC CE 6.1.3.4A Absolute Timing Advance Command MAC CE

The Absolute Timing Advance Command MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-lb.

It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.4a-1): - Timing Advance Command: This field indicates the index value TA used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the field is 12 bits;

FIG. 6 Is a Reproduction of Figure 6.1.3.4a-1 of 3GPP TS 38.321, V16.5.0: Absolute Timing Advance Command MAC CE 6.1.3.15 TCI State Indication for UE-Specific PDCCH MAC CE

The TCI State Indication for UE-specific PDCCH MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with following fields:

-   Serving Cell ID: This field indicates the identity of the Serving     Cell for which the MAC CE applies. The length of the field is 5     bits. If the indicated Serving Cell is configured as part of a     simultaneousTCl-UpdateList1 or simultaneousTCI-UpdateList2 as     specified in TS 38.331, this MAC CE applies to all theServing Cells     in the set simultaneousTCl-UpdateList1 or simultaneousTCI-     UpdateList2, respectively; -   CORESET ID: This field indicates a Control Resource Set identified     with ControlResourceSetld as specified in TS 38.331, for which the     TCI State is being indicated. In case the value of the field is 0,     the field refers to the Control Resource Set configured by     controlResourceSetZero as specified in TS 38.331 [5]. The length of     the field is 4 bits; -   TCI State ID: This field indicates the TCI state identified by     TCI-StateId as specified in TS 38.331 applicable to the Control     Resource Set identified by CORESET ID field. If the field of CORESET     ID is set to 0, this field indicates a TCI-StateId for a TCI state     of the first 64 TCI-states configured by tci-States-ToAddModList and     tci-States-ToReleaseList in the PDSCH-Config in the active BWP. If     the field of CORESET ID is set to the other value than 0, this field     indicates a TCI-StateId configured by tci-StatesPDCCH-ToAddList and     tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified     by the indicated CORESET ID. The length of the field is 7 bits.

FIG. 7 Is a Reproduction of Figure 6.1.3.15-1 of 3GPP TS 38.321, V16.5.0: TCI State Indication for UE-Specific PDCCH MAC CE 6.1.3.14TCI States Activation/Deactivation for UE-Specific PDSCH MAC CE

The TCI States Activation/Deactivation for UE-specific PDSCH MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a variable size consisting of following fields:

-   Serving Cell ID: This field indicates the identity of the Serving     Cell for which the MAC CE applies. The length of the field is 5     bits. If the indicated Serving Cell is configured as part of a     simultaneousTCl-UpdateList1 or simultaneousTCI-UpdateList2 as     specified in TS 38.331, this MAC CE applies to all the Serving Cells     configured in the set simultaneousTCl-UpdateList1 or     simultaneousTCl-UpdateList2, respectively; -   BWP ID: This field indicates a DL BWP for which the MAC CE applies     as the codepoint of the DCI bandwidth part indicator field as     specified in TS 38.212 . The length of the BWP ID field is 2 bits.     This field is ignored if this MAC CE applies to a set of Serving     Cells; -   T_(i): If there is a TCI state with TCI-StateId i as specified in TS     38.331, this field indicates the activation/deactivation status of     the TCI state with TCI-StateId i, otherwise MAC entity shall ignore     the T_(i) field. The T_(i) field is set to 1 to indicate that the     TCI state with TCI-StateId i shall be activated and mapped to the     codepoint of the DCI Transmission Configuration Indication field, as     specified in TS 38.214 [7]. The T_(i) field is set to 0 to indicate     that the TCI state with TCI-StateId i shall be deactivated and is     not mapped to the codepoint of the DCI Transmission Configuration     Indication field. The codepoint to which the TCI State is mapped is     determined by its ordinal position among all the TCI States with     T_(i) field set to 1, i.e. the first TCI State with T_(i) field set     to 1 shall be mapped to the codepoint value 0, second TCI State with     T_(i) field set to 1 shall be mapped to the codepoint value 1 and so     on. The maximum number of activated TCI states is 8; -   CORESET Pool ID: This field indicates that mapping between the     activated TCI states and the codepoint of the DCI Transmission     Configuration Indication set by field T_(i) is specific to the     ControlResourceSetId configured with CORESET Pool ID as specified in     TS 38.331 . This field set to 1 indicates that this MAC CE shall be     applied for the DL transmission scheduled by CORESET with the     CORESET pool ID equal to 1, otherwise, this MAC CE shall be applied     for the DL transmission scheduled by CORESET pool ID equal to 0. If     the coresetPoolIndex is not configured for any CORESET, MAC entity     shall ignore the CORESET Pool ID field in this MAC CE when receiving     the MAC CE. If the Serving Cell in the MAC CE is configured in a     cell list that contains more than one Serving Cell, the CORSET Pool     ID field shall be ignored when receiving the MAC CE.

FIG. 8 Is a Reproduction of Figure 6.1.3.14-1 of 3GPP TS 38.321, V16.5.0: TCI States Activation/Deactivation for UE-Specific PDSCH MAC CE 6.1.3.24Enhanced TCI States Activation/Deactivation for UE-Specific PDSCH MAC CE

The Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE is identified by a MAC PDU subheader with eLCID as specified in Table 6.2.1-lb. It has a variable size consisting of following fields:

-   Serving Cell ID: This field indicates the identity of the Serving     Cell for which the MAC CE applies. The length of the field is 5     bits. If the indicated Serving Cell is configured as part of a     simultaneousTCl-UpdateList1 or simultaneousTCI-UpdateList2 as     specified in TS 38.331, this MAC CE applies to all the Serving Cells     configured in the set simultaneousTCl-UpdateList1 or     simultaneousTCl-UpdateList2, respectively; -   BWP ID: This field indicates a DL BWP for which the MAC CE applies     as the codepoint of the DCI bandwidth part indicator field as     specified in TS 38.212 . The length of the BWP ID field is 2 bits; -   C_(i): This field indicates whether the octet containing TCI state     ID_(i),₂ is present. If this field is set to “1”, the octet     containing TCI state ID_(i,2) is present. If this field is set to     “0”, the octet containing TCI state ID_(i,2) is not present; -   TCI state ID_(i,j): This field indicates the TCI state identified by     TCI-StateId as specified in TS 38.331, where i is the index of the     codepoint of the DCI Transmission configuration indication field as     specified in TS 38.212 [9] and TCI state ID_(i,j) denotes the j^(th)     TCI state indicated for the i^(th) codepoint in the DCI Transmission     Configuration Indication field. The TCI codepoint to which the TCI     States are mapped is determined by its ordinal position among all     the TCI codepoints with sets of TCI state ID_(i),_(j) fields, i.e.     the first TCI codepoint with TCI state ID₀,₁ and TCI state ID₀,₂     shall be mapped to the codepoint value 0, the second TCI codepoint     with TCI state ID_(1,1) and TCI state ID₁,₂ shall be mapped to the     codepoint value 1 and so on. The TCI state ID_(i),₂ is optional     based on the indication of the C_(i) field. The maximum number of     activated TCI codepoint is 8 and the maximum number of TCI states     mapped to a TCI codepoint is 2.

FIG. 9 Is a Reproduction of Figure 6.1.3.24-1 of 3GPP TS 38.321, V16.5.0: Enhanced TCI States Activation/Deactivation for UE-Specific PDSCH MAC CE 6.1.3.25 Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE

The Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-lb. It has a variable size with following fields:

-   Serving Cell ID: This field indicates the identity of the Serving     Cell for which the MAC CE applies. The length of the field is 5     bits; -   BWP ID: This field indicates a UL BWP for which the MAC CE applies     as the codepoint of the DCI bandwidth part indicator field as     specified in TS 38.212 . The length of the BWP ID field is 2 bits; -   PUCCH Resource ID: This field contains an identifier of the PUCCH     resource ID identified by PUCCH-ResourceId as specified in TS     38.331, which is to be activated with a spatial relation indicated     by Spatial Relation Info ID field in the subsequent octet. The     length of the field is 7 bits. If the indicated PUCCH Resource ID is     included in a PUCCH Resource Group (configured via     resourceGroupToAddModList as specified in TS 38.331 [5]) of the     indicated UL BWP, no other PUCCH Resources within the same PUCCH     Resource group are indicated in the MAC CE, and this MAC CE applies     to all the PUCCH Resources in the PUCCH Resource group; -   Spatial Relation Info ID: This field contains     PUCCH-SpatialRelationInfold - 1 where PUCCH-SpatialRelationInfold is     the identifier of the PUCCH Spatial Relation Info in PUCCH-Config in     which the PUCCH Resource ID is configured, as specified in TS 38.331     . The length of the field is 6 bits;

FIG. 10 Is a Reproduction of Figure 6.1.3.25-1 of 3GPP TS 38.321, V16.5.0: Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE 6.1.3.26 Enhanced SP/AP SRS Spatial Relation Indication MAC CE

The Enhanced SP/AP SRS Spatial Relation Indication MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-lb. It has a variable size with following fields:

-   A/D: This field indicates whether to activate or deactivate     indicated SP SRS resource set. The field is set to 1 to indicate     activation, otherwise it indicates deactivation. If the indicated     SRS resource set ID is for the AP SRS resource set, MAC entity shall     ignore this field; -   SRS Resource Set’s Cell ID: This field indicates the identity of the     Serving Cell, which contains the indicated SP/AP SRS Resource Set.     If the C field is set to 0, this field also indicates the identity     of the Serving Cell which contains all resources indicated by the     Resource ID_(i) fields. The length of the field is 5 bits; -   SRS Resource Set’s BWP ID: This field indicates a UL BWP as the     codepoint of the DCI bandwidth part indicator field as specified in     TS 38.212, which contains the indicated SP/AP SRS Resource Set. If     the C field is set to 0, this field also indicates the identity of     the BWP which contains all resources indicated by the Resource     ID_(i) fields. The length of the field is 2 bits; -   C: This field indicates whether the octets containing Resource     Serving Cell ID field(s) and Resource BWP ID field(s) are present.     If this field is set to 1, Resource Serving Cell ID field(s) and     Resource BWP ID field(s) are present, otherwise they are not present     so MAC entity shall ignore Resource Serving Cell ID field(s) and     Resource BWP ID field(s); -   SUL: This field indicates whether the MAC CE applies to the NUL     carrier or SUL carrier configuration. This field is set to 1 to     indicate that it applies to the SUL carrier configuration, and it is     set to 0 to indicate that it applies to the NUL carrier     configuration; -   SRS Resource Set ID: This field indicates the SP/AP SRS Resource Set     ID identified by SRS-ResourceSetId as specified in TS 38.331 . The     length of the field is 4 bits; -   F_(i): This field indicates the type of a resource used as a spatial     relationship for SRS resource within SP/AP SRS Resource Set     indicated with SP/AP SRS Resource Set ID field. F₀ refers to the     first SRS resource within the resource set, F₁ to the second one and     so on. The field is set to 1 to indicate NZP CSI-RS resource index     is used, and it is set to 0 to indicate either SSB index or SRS     resource index is used. The length of the field is 1 bit. This field     is only present if MAC CE is used for activation of SP SRS resource     set, i.e. the A/D field is set to 1, or for AP SRS resource set; -   Resource Serving Cell ID_(i): This field indicates the identity of     the Serving Cell on which the resource used for spatial relationship     derivation for SRS resource i is located. The length of the field is     5 bits; -   Resource BWP ID_(i): This field indicates a UL BWP as the codepoint     of the DCI bandwidth part indicator field as specified in TS 38.212,     on which the resource used for spatial relationship derivation for     SRS resource i is located. The length of the field is 2 bits; -   Resource ID_(i): This field contains an identifier of the resource     used for spatial relationship derivation for SRS resource i.     Resource ID₀ refers to the first SRS resource within the resource     set, Resource ID₁ to the second one and so on. If F_(i) is set to 0,     the first bit of this field is always set to 0. If F_(i) is set to     0, and the second bit of this field is set to 1, the remainder of     this field contains SSB-Index as specified in TS 38.331 . If F_(i)     is set to 0, and the second bit of this field is set to 0, the     remainder of this field contains SRS-ResourceId as specified in TS     38.331 [5]. The length of the field is 8 bits. This field is only     present if MAC CE is used for activation of SP SRS resource set,     i.e. the A/D field is set to 1, or for AP SRS resource set;

FIG. 11 Is a Reproduction of Figure 6.1.3.26-1 of 3GPP TS 38.321, V16.5.0: Enhanced SP/AP SRS Spatial Relation Indication MAC CE

In 38.331, Cell configuration and SRS configuration are introduced:

CellGroupConfig

The CellGroupConfig IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells).

CellGroupConfig Information Element

-- Configuration of one Cell-Group: CellGroupConfig :                              := SEQUENCE {    cellGroupId                                        CellGroupId,    rlc-BearerToAddModList                             SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig OPTIONAL,  -- Need N    rlc-BearerToReleaseList                            SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL,  -- Need N    mac-CellGroupConfig                                MAC-CellGroupConfig OPTIONAL,  -- Need M    physicalCellGroupConfig                            PhysicalCellGroupConfig OPTIONAL,  -- Need M    spCellConfig                                       SpCellConfig OPTIONAL,  -- Need M    sCellToAddModList                                  SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig OPTIONAL,  -- Need N    sCellToReleaseList                                 SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex OPTIONAL,  -- Need N    ...,    [[    reportUplinkTxDirectCurrent                        ENUMERATED {true} OPTIONAL  -- Cond BWP-Reconfig    ]],    [[    bap-Address-r16                                    BIT STRING (SIZE (10)) OPTIONAL,  -- Need M    bh-RLC-ChannelToAddModList-r16                     SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC- ChannelConfig-r16 OPTIONAL,  -- Need N    bh-RLC-ChannelToReleaseList-r16                    SEQUENCE (SIZE(l..maxBH-RLC-ChannelID-r16)) OF BH-RLC- ChannelID-r16     OPTIONAL,  -- Need N    flc-TransferPath-r16                               ENUMERATED {lte, nr, both} OPTIONAL,  -- Need M    simultaneousTCI-UpdateList1-r16                    SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex     OPTIONAL,  -- Need R    simultaneousTCI-UpdateList2-r16                    SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex     OPTIONAL,  -- Need R    simultaneousSpatial-UpdatedList1-r16               SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex     OPTIONAL,  -- Need R    simultaneousSpatial-UpdatedList2-r16               SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex     OPTIONAL,  -- Need R    uplinkTxSwitchingOption-r16                        ENUMERATED {switchedUL, dualUL} OPTIONAL,  -- Need R    uplinkTxSwitchingPowerBoosting-r16                 ENUMERATED {enabled} OPTIONAL   -- Need R    ]],    [[    reportUplinkTxDirectCurrentTwoCarrier-r16 ENUMERATED {true} OPTIONAL -- Need N    ]] }

MAC-CellGroupConfig

The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX.

MAC-CellGroupConfig Information Element

MAC-CellGroupConfig ::=              SEQUENCE {    drx-Config                            SetupRelease { DRX-Config } OPTIONAL,  -- Need M    schedulingRequestConfig               SchedulingRequestConfig OPTIONAL,  -- Need M    bsr-Config                            BSR-Config OPTIONAL,  -- Need M    tag-Config                            TAG-Config OPTIONAL,  -- Need M

ControlResourceSet

The IE ControlResourceSet is used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213 [13], clause 10.1).

ControlResourceSet Information Element

ControlResourceSet ::=                  SEQUENCE {    controlResourceSetId                     ControlResourceSetId,    frequencyDomainResources                 BIT STRING (SIZE (45)),    duration                                 INTEGER (1..maxCoReSetDuration),    cce-REG-MappingType                      CHOICE {        interleaved                              SEQUENCE {            reg-BundleSize                           ENUMERATED {n2, n3, n6},             interleaverSize                         ENUMERATED {n2, n3, n6},             shiftIndex                              INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL -- Need S        },        nonlnterleaved                           NULL    },    precoderGranularity                      ENUMERATED {sameAsREG-bundle, allContiguousRBs},    tci-StatesPDCCH-ToAddList                SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB1-initialBWP    tci-StatesPDCCH-ToReleaseList            SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB1-initialBWP    tci-PresentInDCI                             ENUMERATED {enabled} OPTIONAL, -- Need S    pdcch-DMRS-ScramblingID                      INTEGER (0..65535) OPTIONAL, -- Need S    ...,    [ [    rb-Offset-r16                            INTEGER (0..5) OPTIONAL, -- Need S    tci-PresentDCI-1-2-r16                   INTEGER (1..3) OPTIONAL, -- Need S    coresetPoolIndex-r16                     INTEGER (0..1) OPTIONAL, -- Need S    controlResourceSetId-v1610               ControlResourceSetId-v1610 OPTIONAL -- Need S    ]] }

ControlResourceSet field descriptions cce-REG-MappingType Mapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). controlResourceSetld Identifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1. The controlResourceSetld is unique among the BWPs of a serving cell. If the field controlResourceSetld-v1610 is present, the UE shall ignore the controlResourceSetld field (without suffix). coresetPoollndex The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0. duration Contiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2). frequencyDomainResources Frequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group in the BWP. When at least one search space is configured with freqMonitorLocation-r16, only the first N_(RGB,set0)^(size) bits are valid (see TS 38.213 [13], clause 10.1). The first (left-most / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2). interleaverSize Interleaver-size (see TS 38.211 [16], clause 7.3.2.2). pdcch-DMRS-ScramblingID PDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellld configured for this serving cell. precoderGranularify Precoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). rb-Offset Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1). When the field is absent, the UE applies the value 0. reg-BundleSize Resource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2). shiftlndex When the field is absent the UE applies the value of the physCellldconfigured for this serving cell (see TS 38.211 [16], clause 7.3.2.2). tci-PresentlnDCI This field indicates if TCI field is present or absent in DCI format 1_1. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5). tci-PresentDCI-1-2 Configures the number of bits for “Transmission configuration indicator” in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the “Transmission configuration indicator” in DCI format 1_2 (see TS 38.212, clause 7.3.1 and TS 38.214, clause 5.1.5). tci-StatesPDCCH-ToAddList A subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most maxNrofTCI-StatesPDCCH entries.

ServingCellConfigCommon

The IE ServingCellConfigCommon is used to configure cell specific parameters of a UE’s serving cell. The IE contains parameters which a UE would typically acquire from SSB, MIB or SIBs when accessing the cell from IDLE. With this IE, the network provides this information in dedicated signalling when configuring a UE with a SCells or with an additional cell group (SCG). It also provides it for SpCells (MCG and SCG) upon reconfiguration with sync.

ServingCellConfigCommon Information Element

ServingCellConfigCommon ::=          SEQUENCE {    physCellld                            PhysCellId OPTIONAL,  -- Cond HOAndServCellAdd,    downlinkConfigCommon                  DownlinkConfigCommon OPTIONAL,  -- Cond HOAndServCellAdd    uplinkConfigCommon                    UplinkConfigCommon OPTIONAL,  -- Need M    supplementaryUplinkConfig             UplinkConfigCommon OPTIONAL,  -- Need S    n-TimingAdvanceOffset                 ENUMERATED { n0, n25600, n39936 } OPTIONAL,  -- Need S    ssb-PositionsInBurst                  CHOICE {        shortBitmap                           BIT STRING (SIZE (4)),        mediumBitmap                          BIT STRING (SIZE (8)),        longBitmap                            BIT STRING (SIZE (64))    } OPTIONAL, -- Cond AbsFreqSSB    ssb-periodicityServingCell            ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 }  OPTIONAL, -- Need S    dmrs-TypeA-Position                       ENUMERATED {pos2, pos3},    lte-CRS-ToMatchAround                     SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M    rateMatchPatternToAddModList              SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N    rateMatchPatternToReleaseList             SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N    ssbSubcarrierSpacing                  SubcarrierSpacing OPTIONAL, -- Cond HOAndServCellWithSSB    tdd-UL-DL-ConfigurationCommon         TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD    ss-PBCH-BlockPower                    INTEGER (-60..50),    ...,    [[    channelAccessMode-r16                 CHOICE {        dynamic                               NULL,        semiStatic                            SemiStaticChannelAccessConfig-r16    } OPTIONAL, -- Cond SharedSpectrum    discoveryBurstWindowLength-r16            ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need R    ssb-PositionQCL-r16                       SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum    highSpeedConfig-r16                       HighSpeedConfig-r16 OPTIONAL -- Need R    ]] }

ServingCellConfigCommon field descriptions channelAccessMode If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as “semiStatic”, the UE shall apply the channel access procedures for semi-static channel occupancy as described in subclause 4.3 in TS 37.213. If the field is configured as “dynamic”, the UE shall apply the channel access procedures in TS 37.213, with the exception of subclause 4.3 of TS 37.213. dmrs-TypeA-Position Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.1) and uplink (TS 38.211 [16], clause 6.4.1.1.3). downlinkConfigCommon The common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent. discoveryBurstWindowLength Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). longBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. lte-CRS-ToMatchAround Parameters to determine an LTE CRS pattern that the UE shall rate match around. mediumBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. n-TimingAdvanceOffset The N_TA-Offset to be applied for all uplink transmissions on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2. rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see TS 38.214 [19], clause 5.1.4,1). shortBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1. ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. ssb-periodicityServingCell The SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1) ssb-PositionQCL Indicates the QCL relation between SSB positions for this serving cell as specified in TS 38.213 [13], clause 4.1. ssb-PositionslnBurst For operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access, only mediumBitmap is used and the UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by ssb-PositionsInBurst (see TS 38.213 [13], clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k- 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1’s in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. supplementaryUplinkConfig The network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured. tdd-UL-DL-ConfigurationCommon A cell-specific TDD UL/DL configuration, see TS 38.213 [13], clause 11.1.

TAG-Config

The IE TAG-Config is used to configure parameters for a time-alignment group.

TAG-Config Information Element

TAG-Config ::=                     SEQUENCE {    tag-ToReleaseList                   SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG-Id OPTIONAL,  -- Need N    tag-ToAddModList                    SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG OPTIONAL   -- Need N } TAG :: =                           SEQUENCE {    tag-Id                              TAG-Id,    timeAlignmentTimer                  TimeAlignmentTimer, } TAG-Id ::=                         INTEGER (0..maxNrofTAGs-l) TimeAlignmentTimer ::=             ENUMERATED {ms500, ms750, ms1280, ms1920, ms2560, ms5120, ms10240, infinity)

TAG field descriptions tag-Id Indicates the TAG of the SpCell or an SCell, see TS 38.321 [3]. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG). timeAlignmentTimer Value in ms of the timeAlignmentTimerfor TAG with ID tag-Id, as specified in TS 38.321 [3].

SRS-Config

The IE SRS-Config is used to configure sounding reference signal transmissions. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the set of SRS-Resources or SRS-PosResources using a configured aperiodicSRS-ResourceTrigger (L1 DCI).

SRS-Config Information Element

SRS-Config ::=                      SEQUENCE {    srs-ResourceSetToReleaseList            SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSetId                 OPTIONAL, -- Need N    srs-ResourceSetToAddModList             SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSet                   OPTIONAL, -- Need N    srs-ResourceToReleaseList               SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS- ResourceId                       OPTIONAL, -- Need N    srs-ResourceToAddModList                SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL,  -- Need N    tpc-Accumulation                        ENUMERATED {disabled} OPTIONAL,  -- Need S    ...,    [[    srs-RequestDCI-1-2-r16                  INTEGER (1..2) OPTIONAL, -- Need S    srs-RequestDCI-0-2-r16                  INTEGER (1..2) OPTIONAL, -- Need S    srs-ResourceSetToAddModListDCI-0-2-r16  SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSet         OPTIONAL, -- Need N    srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSetId       OPTIONAL, -- Need N    srs-PosResourceSetToReleaseList-r16     SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N    srs-PosResourceSetToAddModList-r16      SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16       OPTIONAL,-- Need N    srs-PosResourceToReleaseList-r16        SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS- PosResourceId-r16           OPTIONAL,-- Need N    srs-PosResourceToAddModList-r16         SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS- PosResource-r16             OPTIONAL -- Need N ]] } SRS-ResourceSet ::=                    SEQUENCE {    srs-ResourceSetId                       SRS-ResourceSetId,    srs-ResourceIdList                      SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS- ResourceId   OPTIONAL, -- Cond Setup    resourceType                            CHOICE {        aperiodic                               SEQUENCE {            aperiodicSRS-ResourceTrigger            INTEGER (1..maxNrofSRS-TriggerStates-1),             csi-RS                                 NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook             slotOffset                             INTEGER (1..32) OPTIONAL, -- Need S             ...,             [[             aperiodicSRS-ResourceTriggerList           SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates- 2))                                                                  OF INTEGER (1..maxNrofSRS-TriggerStates- 1) OPTIONAL -- Need M        ]]    },        semi-persistent                         SEQUENCE {            associatedCSI-RS                        NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook            ...        },        periodic                                SEQUENCE {            associatedCSI-RS                        NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook        }    },    usage                                  ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},    alpha                                  Alpha OPTIONAL, -- Need S    p0                                     INTEGER (-202..24) OPTIONAL, -- Cond Setup    pathlossReferenceRS                    PathlossReferenceRS-Config OPTIONAL, -- Need M    srs-PowerControlAdjustmentStates       ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S    ...,    [[    pathlossReferenceRSList-r16            SetupRelease {PathlossReferenceRSList-r16} OPTIONAL -- Need M ]] } PathlossReferenceRS-Config ::=            CHOICE {    ssb-Index                                  SSB-Index,    csi-RS-Index                               NZP-CSI-RS-ResourceId } PathlossReferenceRSList-r16 ::=           SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16 PathlossReferenceRS-r16 ::=               SEQUENCE {    srs-PathlossReferenceRS-Id-r16             SRS-PathlossReferenceRS-Id-r16,    pathlossReferenceRS-r16                    PathlossReferenceRS-Config } SRS-PathlossReferenceRS-Id-r16 ::=         INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16) SRS-PosResourceSet-r16 ::=                 SEQUENCE {    srs-PosResourceSetId-r16                    SRS-PosResourceSetId-r16,    srs-PosResourceIdList-r16                   SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16 OPTIONAL, -- Cond Setup    resourceType-r16                            CHOICE {        aperiodic-r16                               SEQUENCE {            aperiodicSRS-ResourceTriggerList-r16        SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates- 1))                                                                  OF INTEGER (1..maxNrofSRS-TriggerStates- 1)            OPTIONAL, -- Need M           ...        },        semi-persistent-r16                        SEQUENCE {           ...        },        periodic-r16                               SEQUENCE {           ...        }    },    alpha-r16                                   Alpha OPTIONAL, -- Need S    p0-r16                                      INTEGER (-202..24) OPTIONAL, -- Cond Setup    pathlossReferenceRS-Pos-r16                 CHOICE {        ssb-IndexServing-r16                        SSB-Index,        ssb-Ncell-r16                               SSB-InfoNcell-r16,        dl-PRS-r16                                  DL-PRS-Info-r16    } OPTIONAL, -- Need M           ... } SRS-ResourceSetId ::=                          INTEGER (0..maxNrofSRS-ResourceSets-1) SRS-PosResourceSetId-r16 ::=                   INTEGER (0..maxNrofSRS-PosResourceSets-1-r16) SRS-Resource ::=                               SEQUENCE {    srs-ResourceId                                  SRS-ResourceId,    nrofSRS-Ports                                   ENUMERATED {port1, ports2, ports4},    ptrs-PortIndex                                  ENUMERATED {n0, n1} OPTIONAL,  -- Need R    transmissionComb                                CHOICE {        n2                                              SEQUENCE {             combOffset-n2                                  INTEGER (0..1),             cyclicShift-n2                                 INTEGER (0..7)        },        n4                                                  SEQUENCE {             combOffset-n4                                      INTEGER (0..3),             cyclicShift-n4                                     INTEGER (0..11)        }    },    resourceMapping                                 SEQUENCE {        startPosition                                   INTEGER (0..5),        nrofSymbols                                     ENUMERATED {n1, n2, n4},        repetitionFactor                                ENUMERATED {n1, n2, n4}    },    freqDomainPosition                              INTEGER (0..67),    freqDomainShift                                 INTEGER (0..268),    freqHopping                                     SEQUENCE {        c-SRS                                           INTEGER (0..63),        b-SRS                                           INTEGER (0..3),        b-hop                                           INTEGER (0..3)    },    groupOrSequenceHopping                          ENUMERATED { neither, groupHopping, sequenceHopping },    resourceType                                    CHOICE {        aperiodic                                       SEQUENCE {           ...        },        semi-persistent                                 SEQUENCE {            periodicityAndOffset-sp                             SRS-PeriodicityAndOffset,           ...        },        periodic                                        SEQUENCE {            periodicityAndOffset-p                              SRS-PeriodicityAndOffset,           ...        }    },    sequenceId                                      INTEGER (0..1023),    spatialRelationInfo                             SRS-SpatialRelationInfo OPTIONAL, -- Need R    ...,    [ [    resourceMapping-r16                             SEQUENCE {        startPosition-r16                               INTEGER (0..13),        nrofSymbols-r16                                 ENUMERATED {n1, n2, n4},        repetitionFactor-r16                            ENUMERATED {n1, n2, n4}    } OPTIONAL -- Need R    ]] } SRS-PosResource-r16::=                          SEQUENCE {    srs-PosResourceId-r16                            SRS-PosResourceId-r16,    transmissionComb-r16                             CHOICE {        n2-r16                                           SEQUENCE {             combOffset-n2-r16                               INTEGER (0..1),             cyclicShift-n2-r16                              INTEGER (0..7)        },        n4-r16                                           SEQUENCE {             combOffset-n4-r16                                INTEGER (0..3),             cyclicShift-n4-r16                               INTEGER (0..11)        },        n8-r16                                           SEQUENCE {             combOffset-n8-r16                               INTEGER (0..7),             cyclicShift-n8-r16                              INTEGER (0..5)        },    ...    },    resourceMapping-r16                              SEQUENCE {        startPosition-r16                                  INTEGER (0..13),        nrofSymbols-r16                                    ENUMERATED {n1, n2, n4, n8, n12}    },    freqDomainShift-r16                              INTEGER (0..268),    freqHopping-r16                                  SEQUENCE {        c-SRS-r16                                        INTEGER (0..63),        ...    },    groupOrSequenceHopping-r16                       ENUMERATED { neither, groupHopping, sequenceHopping },    resourceType-r16                                 CHOICE {        aperiodic-r16                                    SEQUENCE {             slotOffset-r16                                  INTEGER (1..32) OPTIONAL, -- Need S           ...        },        semi-persistent-r16                              SEQUENCE {            periodicityAndOffset-sp-r16                      SRS-PeriodicityAndOffset-r16,           ...        },        periodic-r16                                     SEQUENCE {            periodicityAndOffset-p-r16                       SRS-PeriodicityAndOffset-r16,            ...        }    },    sequenceId-r16                                   INTEGER (0..65535),    spatialRelationInfoPos-r16                       SRS-SpatialRelationInfoPos-r16 OPTIONAL,  -- Need R    ... } SRS-SpatialRelationInfo ::=     SEQUENCE {    servingCellId                        ServCellIndex OPTIONAL,  -- Need S    referenceSignal                      CHOICE {        ssb-Index                            SSB-Index,        csi-RS-Index                         NZP-CSI-RS-ResourceId,        srs                                  SEQUENCE {            resourceId                           SRS-ResourceId,            uplinkBWP                            BWP-Id        }    } } SRS-SpatialRelationInfoPos-r16 ::=      CHOICE {    servingRS-r16                            SEQUENCE {        servingCellId                            ServCellIndex OPTIONAL,  -- Need S        referenceSignal-r16                      CHOICE {             ssb-IndexServing-r16                    SSB-Index,             csi-RS-IndexServing-r16                 NZP-CSI-RS-ResourceId,             srs-SpatialRelation-r16                 SEQUENCE {                 resourceSelection-r16                   CHOICE {                     srs-ResourceId-r16                      SRS-ResourceId,                     srs-PosResourceId-r16                   SRS-PosResourceId-r16                 },                 uplinkBWP-r16                           BWP-Id             }        }    },    ssb-Ncell-r16                                SSB-InfoNcell-r16,    dl-PRS-r16                                   DL-PRS-Info-r16 } SSB-Configuration-r16 ::=     SEQUENCE {    ssb-Freq-r16               ARFCN-ValueNR,    halfFrameIndex-r16            ENUMERATED {zero, one},    ssbSubcarrierSpacing-r16      SubcarrierSpacing,    ssb-Periodicity-r16           ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1 }  OPTIONAL, -- Need S    sfn0-Offset-r16               SEQUENCE {        sfn-Offset-r16                       INTEGER (0..1023),        integerSubframeOffset-r16            INTEGER (0..9) OPTIONAL -- Need R    } OPTIONAL, -- Need R    sfn-SSB-Offset-r16                    INTEGER (0..15),    ss-PBCH-BlockPower-rl6                INTEGER (-60..50) OPTIONAL  -- Cond Pathloss } SSB-InfoNcell-r16 ::=                SEQUENCE {    physicalCellId-r16                    PhysCellId,    ssb-IndexNcell-r16                    SSB-Index OPTIONAL,  -- Need S    ssb-Configuration-r16                 SSB-Configuration-r16 OPTIONAL -- Need S } DL-PRS-Info-r16 ::=                  SEQUENCE {    dl-PRS-ID-r16                        INTEGER (0..255),    dl-PRS-ResourceSetId-r16             INTEGER (0..7),    dl-PRS-ResourceId-r16                INTEGER (0..63) OPTIONAL -- Need S } SRS-ResourceId ::=                       INTEGER (0..maxNrofSRS-Resources-1) SRS-PosResourceId-r16 ::=                INTEGER (0..maxNrofSRS-PosResources-1-r16) SRS-PeriodicityAndOffset ::=             CHOICE {    sl1                                       NULL,    sl2                                       INTEGER(0..1),    sl4                                       INTEGER(0..3),    sl5                                       INTEGER(0..4),    sl8                                       INTEGER(0..7),    sl10                                      INTEGER(0..9),    sl16                                      INTEGER(0..15),    sl20                                      INTEGER(0..19),    sl32                                      INTEGER(0..31),    sl40                                      INTEGER(0..39),    sl64                                      INTEGER(0..63),    sl80                                      INTEGER(0..79),    sl160                                     INTEGER(0..159),    sl320                                     INTEGER(0..319),    sl640                                     INTEGER(0..639),    sl1280                                    INTEGER(0..1279),    sl2560                                    INTEGER(0..2559) } SRS-PeriodicityAndOffset-r16 ::=        CHOICE {    sl1                                      NULL,    sl2                                      INTEGER(0..1),    sl4                                      INTEGER(0..3),    sl5                                      INTEGER(0..4),    sl8                                      INTEGER(0..7),    sl10                                     INTEGER(0..9),    sl16                                     INTEGER(0..15),    sl20                                     INTEGER(0..19),    sl32                                     INTEGER(0..31),    sl40                                     INTEGER(0..39),    sl64                                     INTEGER(0..63),    sl80                                     INTEGER(0..79),    sl160                                    INTEGER(0..159),    sl320                                    INTEGER(0..319),    sl640                                    INTEGER(0..639),    sl1280                                   INTEGER(0..1279),    sl2560                                   INTEGER(0..2559),    sl5120                                   INTEGER(0..5119),    sl10240                                  INTEGER(0..10239),    sl40960                                  INTEGER(0..40959),    sl81920                                  INTEGER(0..81919), }

SRS-Config field descriptions tpc-Accumulation If the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see TS 38.213 [13], clause 7.3). SRS-Resource, SRS-PosResource field descriptions cyclicShift-n2 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). cyclicShift-n4 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). freqHopping Includes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS. groupOrSequenceHopping Parameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to ‘neither’. nrofSRS-Ports Number of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to ‘port1’. periodicityAndOffsef-p Periodicity and slot offset for this SRS resource. All values are in “number of slots”. Value s/1 corresponds to a periodicity of 1 slot, value s/2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity s/1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, s/1280 and s/2560 cannot be configured. periodicityAndOffset-sp Periodicity and slot offset for this SRS resource. All values are in “number of slots”. Value s/1 corresponds to a periodicity of 1 slot, value s/2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity s/1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). ptrs-PortIndex The PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-Portlndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see TS 38.214 [19], clause 6.2.3.1). This parameter is not applicable to CLI SRS-RSRP measurement. resourceMapping OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactorto ‘n1’. resourceType Periodicity and offset for semi-persistent and periodic SRS resource (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, only ‘periodic’ is applicable for resource Type. sequenceld Sequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1). servingCellId The serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured. spatialRelationInfo Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see TS 38.214 [19], clause 6.2.1). This parameter is not applicable to CLI SRS-RSRP measurement. spatialRelationInfoPos Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see TS 38.214 [19], clause 6.2.1). If the IE srs-Resourceld-Ext is present, the IE srs-Resourceld in spatialRelationlnfoPos represents the index from 0 to 63. Otherwise the IE srs-Resourceld in spatialRelationlnfoPos represents the index from 0 to 31. srs-RequestDCI-0-2 Indicate the number of bits for “SRS request”in DCI format 0_2. When the field is absent, then the value of 0 bit for “SRS request” in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 [17] for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212 [17]. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication. srs-RequestDCI-1-2 Indicate the number of bits for “SRS request” in DCI format 1_2. When the field is absent, then the value of 0 bit for “SRS request” in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see TS 38.214 [19], clause 6.1.1.2). srs-ResourceSetToAddModListDCI-0-2 List of SRS resource set to be added or modified for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). srs-ResourceSetToReleaseLisfDCl-0-2 List of SRS resource set to be released for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). transmissionComb Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1). SRS-ResourceSef, SRS-PosResourceSef field descriptions alpha alpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1. aperiodicSRS-ResourceTriggerList An additional list of DCI “code points” upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resource Type set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3. aperiodicSRS-ResourceTrigger The DCI “code point” upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). associatedCSI-RS ID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2). csi-RS ID of CSI-RS resource associated with this SRS resource set. (see TS 38.214 [19], clause 6.1.1.2). csi-RS-indexServingcell Indicates CSI-RS index belonging to a serving cell p0 P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3). pathlossReferenceRS A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). pathlossReferenceRS-Pos A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). pathlossReferenceRSList Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321 [3]). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet. resourceSelection Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource. resourceType Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS. slotOffset An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0). srs-PowerControlAdjustmentStates Indicates whether hsrs,c(i) ₌ fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for Uls on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see TS 38.213 [13], clause 7.3). srs-ResourceldList, srs-PosResourceldList The IDs of the SRS-Resources/SRS-PosResource used in this SRS-ResourceSet/SRS-PosResourceSet. If this SRS-ResourceSet/SRS-PosResourceSet is configured with usage set to codebook, the srs-ResourceldList/srs-PosResourceldList contains at most 2 entries. If this SRS-ResourceSet/SRS-PosResourceSet is configured with usage set to nonCodebook, the srs-ResourceldList/srs-PosResourceldList contains at most 4 entries. srs-ResourceSetld, srs-PosResourceSetld The ID of this resource set. It is unique in the context of the BWP in which the parent SRS-Config is defined. ssb-IndexSevingcell Indicates SSB index belonging to a serving cell ssb-NCell This field indicates a SSB configuration from neighboring cell usage Indicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See TS 38.214 [19], clause 6.2.1. Reconfiguration between codebook based and non-codebook based transmission is not supported.

In 3GPP specification 38.211[5], frame structure is introduced:

-   N_(TA) Timing advance between downlink and uplink; see clause 4.3.1 -   N_(TAoffset) A fixed offset used to calculate the timing advance;     see clause 4.3.1

4.3 Frame Structure 4.3.1 Frames and Subframes

Downlink, uplink, and sidelink transmissions are organized into frames with T_(f) = (Δf_(max)N_(f)/100).T_(c) ₌10 ms duration, each consisting of ten subframes of T_(sf) ₌ (Δf_(max)N_(f)/1000). T_(c) = 1 ms duration. The number of consecutive OFDM symbols per subframe is Each frame is divided into two equally-sized half-frames of five subframes each with half-frame 0 consisting of subframes 0 - 4 and half-frame 1 consisting of subframes 5 - 9. There is one set of frames in the uplink and one set of frames in the downlink on a carrier. Uplink frame number i for transmission from the UE shall start T_(TA) = (N_(TA) + N_(TA),_(offset))T_(c) before the start of the corresponding downlink frame at the UE where NT_(A),_(offset) is given by [5, TS 38.213], except for msgA transmission on PUSCH where N_(TA) = 0 shall be used.

FIG. 12 is a Reproduction of FIG. 4.3.1-1 of 3GPP TS 38.211, V16.6.0: Uplink-Downlink Timing Relation

In [6], DCI format 1_0 is cited below:

7.3.1.2.1Format 1_0

DCI format 1_0 is used for the scheduling of PDSCH in one DL cell.

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

-   Identifier for DCI formats - 1 bits -   The value of this bit field is always set to 1, indicating a DL DCI     format -   Frequency domain resource assignment - bits where is given by clause     7.3.1.0

If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the “Frequency domain resource assignment” field are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows:

-   Random Access Preamble index - 6 bits according to ra-PreambleIndex     in Clause 5.1.2 of [8, TS38.321] -   UL/SUL indicator - 1 bit. If the value of the “Random Access     Preamble index” is not all zeros and if the UE is configured with     supplementary Uplink in ServingCellConfig in the cell, this field     indicates which UL carrier in the cell to transmit the PRACH     according to Table 7.3.1.1.1-1; otherwise, this field is reserved -   SS/PBCH index - 6 bits. If the value of the “Random Access Preamble     index” is not all zeros, this field indicates the SS/PBCH that shall     be used to determine the RACH occasion for the PRACH transmission;     otherwise, this field is reserved. -   PRACH Mask index - 4 bits. If the value of the “Random Access     Preamble index” is not all zeros, this field indicates the RACH     occasion associated with the SS/PBCH indicated by “SS/PBCH index”     for the PRACH transmission, according to Clause 5.1.1 of [8,     TS38.321]; otherwise, this field is reserved -   Reserved bits - 12 bits for operation in a cell with shared spectrum     channel access; otherwise 10 bits

In New Radio (NR) enhancements to multiple-input/multiple-out (eMIMO) work item, multi-Transmission/Reception Point (TRP) (or mTRP) operation is introduced. A User Equipment (UE) could perform communication with a cell of a network (e.g., gNB) via more than one TRP of the cell. In Rel-16, multi-Physical Downlink Shared Channel (PDSCH) transmission is introduced. The UE could be indicated with two (activated) Transmission Configuration Indicator (TCI) states for receiving (two) PDSCH transmission occasions. Each TCI state could be associated with a PDSCH transmission. The PDSCH transmissions could have non-overlapping frequency and/or time domain resource allocation with respect to the other PDSCH transmission occasion. In NR release 17 work item on mimo enhancements ([1] RP-193133 New WID: Further enhancements on MIMO for NR), multi-TRP transmission for Physical Uplink Shared Channel (PUCCH), Physical Uplink Shared Channel (PUSCH) and Physical Downlink Control Channel (PDCCH) is introduced. The goal of multi-TRP PUSCH is for the UE to transmit a same data via multiple PUSCH to a network to achieve reliability (e.g., using spatial diversity of multiple TCI states or beams or spatial relation info). In Rel-17, inter-cell multi-TRP (or mTRP) operation is introduced. That is, a UE could be performing communication via a first TRP from a serving cell and a second TRP from a non-serving cell (e.g., a cell with a physical cell identity, Physical Cell Identity (PCI), different from a serving cell). In Rel-18 RAN workshop, (simultaneous) Uplink (UL) transmission via multi-panel is introduced. For an example, a UE could perform UL transmission on a serving cell using a first panel of the UE, and perform UL transmission on a non-serving cell using a second panel of the UE. In releases before Rel-17, mechanisms are designed that the TRPs in multi-TRP operation (in the same cell or across different cells) are synchronous. The UE could have the same UL time alignment (TA) among the TRPs when performing mTRP operation. In other words, the UE could perform UL transmission to TRPs in a mTRP operation by applying a single TA. In Rel-18, a more realistic scenario is discussed. Different TRPs could be in different location (e.g., may not be co-located) and may not be synchronous in a UE’s perspective (that is, the TRPs could be asynchronous). In this invention, the mechanisms on how to obtain and/or maintain TA for asynchronous TRPs (associated with a same cell or different cells) in a multi-TRP operation.

Inter-cell mTRP UE-Random Access Channel (RACH) obtains TA

One concept of the invention is that a UE performing multi-TRP (mTRP) operation on a first TRP and a second TRP, the UE could obtain a first TA information associated with the first TRP and a second TA information associated with the second TRP. For a UE configured with UL resource(s) on a non-Serving Cell, the UE could initiate a random access procedure on (a TRP of) the non-Serving Cell. The UE could initiate the random access procedure to obtain TA information associated with (the TRP of) the non-Serving Cell. The UE could perform multi-TRP (mTRP) operation associated with the TRP on the non-Serving Cell (and another TRP on a Serving Cell). The UE may not consider the non-Serving Cell to be Serving cell (e.g., does not consider as a Secondary Cell or a Primary Cell) after completion of the random access procedure.

For example, the UE could perform mTRP operation on a first TRP on the non-Serving Cell and a second TRP on a Serving Cell. The UE could obtain a TA information associated with (the second TRP of) the Serving Cell via a previous random access procedure. The UE may not obtain the TA information associated with the non-Serving Cell via the previous random access procedure. The first TRP and the second TRP are not synchronous (e.g., the UE has different N_(TA) and/or N_(TA),_(offset) for the first TRP and the second TRP).

The UE could initiate a (latter) random access procedure on the first TRP (associated with the non-Serving Cell) in response to a signaling from the network. The signaling could be a PDCCH signaling (e.g., PDCCH order-like signal). The signaling could indicate the non-Serving Cell (e.g., indicates physical cell identity of the non-Serving Cell). The signaling could indicate the first TRP (e.g., indicates TCI state(s) and/or coresetpool index and/or Sounding Reference Signal (SRS) resource set(s) or spatial relation info or Beam Failure Detection Reference Signal (BFD-RS) set associated with the first TRP). Additionally and/or alternatively, the coresetpool index could be implicitly indicated by on which resource (e.g., Control Resource Set (CORESET)) the UE receives the PDCCH order (or the PDCCH signaling).

The (latter) random access procedure could be a contention-free and/or a contention-based random access procedure. The UE could obtain TA information associated with (the first TRP of) the non-Serving Cell from the (latter) random access procedure.

The UE could apply the TA information associated with (the first TRP of) the non-Serving Cell for UL transmissions on the first TRP of the non-Serving Cell. The UE could apply the TA information associated with (the second TRP of) the Serving Cell for UL transmissions on the second TRP of the Serving Cell.

Additionally and/or alternatively, the UE could determine whether to initiate a random access procedure on the (TRPs of) non-Serving Cell based on at least TA information is provided/configured when the non-Serving Cell is configured and/or activated. The UE may not initiate a random access procedure on the (TRPs of) non-Serving Cell if TA information of the (TRPs of) non-Serving Cell is provided or configured.

Additionally and/or alternatively, the UE could determine whether to initiate a random access procedure on the (TRPs of) non-Serving Cell based on at least whether resources and/or configurations for random access procedure on the non-Serving Cell is provided (by the network). The UE may not initiate a random access procedure on the (TRPs of) non-Serving Cell if no resources and/or configurations for random access procedure on the non-Serving Cell is provided.

The UE could initiate the random access procedure on the non-Serving Cell in response to an activation of a TCI state or spatial relation info associated with the non-Serving Cell. Additionally and/or alternatively, the UE could initiate the random access procedure on the non-Serving Cell in response to an activation of a TRP associated with the non-Serving Cell. Additionally and/or alternatively, the UE could initiate the random access procedure on the non-Serving Cell in response to PDCCH order (or the PDCCH signaling) provided by a network.

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the non-Serving Cell in response to activation of TRPs or TCI state(s) or spatial relation info associated with the non-Serving Cell based on at least whether a TA information (associated with the non-Serving Cell or TRP) is provided when the non-Serving Cell is configured or when the UL resource(s) of the non-Serving Cell is configured. The UE may not initiate the random access procedure on the non-Serving Cell if a TA information associated with the non-Serving Cell was provided when the non-Serving Cell is configured or TA information associated with the TRP.

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the non-Serving Cell in response to an activation signaling of TRPs or TCI state(s) or spatial relation info associated with the non-Serving Cell based on (the content or attribute of) the activation signaling. The UE could determine to initiate the random access procedure on the non-Serving Cell in response to the activation signaling if or when the activation signaling indicates the UE to perform a random access procedure (to obtain TA information of the non-Serving Cell). The UE could determine to not initiate the random access procedure on the non-Serving Cell in response to the activation signaling if or when the activation signaling does not indicate the UE to perform a random access procedure. The UE could apply TA information of the Serving Cell for UL transmissions on the non-Serving Cell (after activation of the non-Serving Cell). The activation signaling could be a PDCCH signaling. The activation signaling could indicate the UE to apply (existing) TA information of a Serving Cell on the non-Serving Cell.

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the non-Serving Cell in response to activation of TRPs or TCI state(s) or spatial relation info associated with the non-Serving Cell based on at least whether there is a valid TA information for the non-Serving Cell or TRP. The UE may not initiate a random access procedure on the non-Serving Cell if there is a valid TA information for the non-Serving Cell when the TRP of the non-Serving Cell is activated. The UE could apply the valid TA information of the non-Serving Cell for UL transmissions on the non-Serving Cell (after activation of the non-Serving Cell). For example, a UE could consider a TA information to be valid when a timer (e.g., timealignmenttimer) associated with the TA information is running.

Additionally and/or alternatively, the UE could stop the timer when the TRP of the non-Serving Cell is deactivated. The UE could consider a TA information to be invalid when a timer (e.g., timealignmenttimer) associated with the TA information is not running.

Intra-Cell mTRP UE-RACH obtains TA

Another concept of the invention is that for a UE performing a mTRP operation on a first TRP on a Cell and a second TRP on the (same) Cell, the UE could initiate a first random access procedure for the first TRP on the Cell to obtain first TA information of the first TRP, and initiate a second random access procedure for the second TRP on the Cell to obtain second TA information of the second TRP.

For example, for a UE configured with UL resource(s) of a serving cell, the UE is configured with a first TRP of the serving Cell for UL transmission. The UE initiates a first random access procedure on the first TRP of the Serving Cell to obtain first TA information of the first TRP (e.g., initiates by a PDCCH order by a network or initiates in response to connection establishment). The UE performs UL and/or Downlink (DL) communication with the first TRP by applying the first TA information of the first TRP. The UE is configured with a second TRP of the Serving Cell. The network could indicates the UE to perform (intra-cell) mTRP operation (e.g., DL or UL transmission) on the first TRP and the second TRP. The network could indicate the UE to perform mTRP operation via an activation signaling, e.g., a TCI states activation Medium Access Control (MAC) Control Element (CE) (or a spatial relation info activation MAC CE) indicating activation of (UL or DL) TCI state(s) (or the spatial relation info) associated with the second TRP. The first TRP and the second TRP are not synchronous. The UE initiates a second random access procedure on the second TRP, in response to the TCI states activation MAC CE (or a spatial relation info activation MAC CE), to obtain second TA information of the second TRP. In response to completion of the second random access procedure, the UE could perform UL and/or DL communication with the second TRP by applying the second TA information of the second TRP (and perform UL and/or DL communication with the first TRP by applying the first TA information). Additionally and/or alternatively, the UE may not initiate the second random access procedure in response to a PDCCH order. The UE initiates the second random access procedure in response to activation of the second TRP or activation of multi-TRP operation. Additionally and/or alternatively, the UE initiates the second random access procedure in response to receiving a PDCCH signaling, wherein the PDCCH signaling indicates the UE to perform UL transmission on a second TRP or activate mTRP operation.

The UE could determine whether to obtain and/or maintain a second TA information (for a second TRP) for a Cell (in addition to a first TA information) via a random access procedure in response to receiving a PDCCH signaling based on at least a format or field of the PDCCH signaling. The UE may not obtain a second TA information if the PDCCH signaling is a PDCCH order (e.g., Downlink Control Information (DCI) format 1-0). The UE could initiate a random access procedure and obtain a second TA information if the PDCCH signaling is not a PDCCH order (e.g., a PDCCH signaling indicates, in a field, a random access procedure for the second TRP). Preferably, the field may be one bit for identifying update current TA or obtain a second TA. Preferably, the field may be reusing one bit in current reserved bit of DCI format 1_0. Additionally and/or alternatively, the UE could determine whether to obtain a second TA information in response to the PDCCH signaling based on at least a resource (e.g., CORESET) on which the UE receives the PDCCH signaling. The UE could initiate the random access procedure on the second TRP in response to the PDCCH signaling (and obtain a second TA information for the second TRP) if or when the PDCCH signaling is received on a CORESET associated with the second TRP. The UE may not initiate the random access procedure on the second TRP in response to the PDCCH signaling if or when the PDCCH signaling is received on a CORESET associated with the first TRP. The UE could update or renew the first TA information of the first TRP if or when the PDCCH signaling is received on a CORESET associated with the first TRP.

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the second TRP in response to an activation signaling (e.g., TCI state or spatial relation info activation MAC CE) associated with the second TRP based on (the content or attribute of) the activation signaling. The UE could determine to initiate the random access procedure on the second TRP in response to the activation signaling if or when the activation signaling indicates the UE to perform a random access procedure (to obtain TA information of the second TRP). The UE could determine to not initiate the random access procedure on the second TRP in response to the activation signaling if or when the activation signaling does not indicate the UE to perform a random access procedure. The UE could apply (the first) TA information of the first TRP for UL transmissions on the second TRP (after activation of the second TRP).

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the second TRP in response to activation of TCI state(s) (or spatial relation info) associated with the second TRP based on at least whether there is a valid TA information for the second TRP. The UE may not initiate a random access procedure on the second TRP if there is a valid TA information for the second TRP when the second TRP is activated. The UE could apply the valid TA information of the second TRP for UL transmissions on the second TRP (after activation of the second TRP). For example, a UE could consider a TA information to be valid when a timer (e.g., timealignmenttimer) associated with the TA information is running. The network could indicate (via Radio Resource Control (RRC) message or activation signaling of the TRP) the UE a valid TA information of the second TRP. The valid TA information could be associated with or the same as the TA information of the first TRP.

Additionally and/or alternatively, the UE could stop the timer when the second TRP of the Serving Cell is deactivated. The UE could consider a TA information to be invalid when a timer (e.g., timealignmenttimer) associated with the TA information is not running.

The first TRP and the second TRP are not synchronous. The UE could maintain different set of N_(TA) and/or NT_(A),_(offset) for the first TRP and the second TRP.

Additionally and/or alternatively, the UE could determine whether to initiate a random access procedure on the second TRP on the Cell based on at least TA information is provided/configured when the second TRP is configured and/or activated. The UE may not initiate a random access procedure on the second TRP if TA information of the second TRP is provided or configured.

Additionally and/or alternatively, the UE could determine whether to initiate the random access procedure on the second TRP in response to activation of the second TRP of the Cell based on at least whether resources and/or configurations for Random access procedure on the second TRP is provided (by the network). The UE may not initiate a random access procedure on the second TRP if no resources and/or configurations for Random access procedure on the second TRP is provided. The resources and/or configuration for random access procedure could be configured/provided in a per-TRP basis (e.g., more than one set of resources in one Cell used for different TRPs/TCI states/spatial relation info).

Additionally and/or alternatively, the network could provide SRS configuration of a SRS resource (set) (e.g., SRS-config) associated with a second TRP of a Cell for the UE. The SRS resource (set) could indicate periodic and/or slot offset of SRS resource(s). The UE could transmit SRS to the second TRP based on the SRS configuration. The UE could (start to) transmit SRS via the SRS resource(s) in response to receiving the SRS configuration (e.g., periodic SRS transmission). Alternatively, the UE could (start to) transmit SRS via the SRS resource(s) in response to receiving an activation signaling of the SRS configuration (e.g., semi-persistent SRS transmission).

The UE could apply the TA information (e.g., Timing Advance N_(TA) and/or offset N_(TA),_(offset)) of the first TRP of the Cell to SRS transmitted via the SRS resource(s) of the second TRP. Alternatively, the UE could apply no (or zero) TA to SRS transmitted via the SRS resource(s) of the second TRP. Alternatively, the UE could apply a previously configured TA information of the second TRP (e.g., via RRC reconfiguration message) to SRS transmitted via the SRS resource(s). The SRS could be transmitted before initiation or completion of the random access procedure.

The UE could transmit the SRS (via SRS resource(s) of the second TRP) via UL beam(s) associated with the second TRP.

In response to activation of the second TRP or indicated by the network, the UE could initiate a random access procedure to the network and obtain a second TA information of the second TRP. The UE could apply or use the second TA information of the second TRP for transmitting the SRS via the SRS resource(s) of the second TRP after or in response to completion of the random access procedure or activation of the second TRP. The UE could apply or use the TA information of the first TRP for transmitting SRS via SRS resource(s) of the first TRP (before and after the random access procedure on the second TRP). The UE could transmit the SRS (via SRS resource(s) of the first TRP) via UL beam(s) associated with the first TRP.

NW-Provided TA

Another concept of the invention is that for a UE performing multi-TRP (mTRP) operation on a first TRP and a second TRP, a network could provide or configure a first TA information associated with the first TRP and a second time alignment information associated with the second TRP. The network could provide a per-TRP TA information to the UE.

The first TRP could be associated with a first Cell (e.g., a Serving Cell of the UE), and the second TRP could be associated with a second Cell (e.g., a non-serving Cell of the UE). The first TRP could be a TRP of the first Cell. The second TRP could be a TRP of the second Cell.

Alternatively, the first TRP and the second TRP could be associated with a same cell (e.g., a serving Cell of the UE or a non-serving Cell of the UE). For the UE, the Cell could be associated with two or more different TA information, which are associated with different TRPs of the Cell.

In one example, for a UE performing UL transmission or configured with UL resources on a TRP of a non-Serving Cell, the network could provide or (pre-)configure a first TA information associated with the non-Serving Cell. Additionally and/or alternatively, the first TA information could be associated with a TRP of the non-Serving Cell (and not associated with other TRPs of the non-Serving Cell). The network could provide the first TA information via a RRC configuration (e.g., RRCReconfiguration message). The network could configure the first TA information of the non-Serving Cell when or in addition to configuring the non-Serving Cell to the UE. The UE may not apply the first TA information in response to receiving the configuration. The UE may not apply the first TA information until the TRP is activated for the UE (to perform UL transmission) and/or the non-Serving Cell is used for mTRP operation.

The first TA information could be associated with a TA of a Serving Cell (or a Timing Advance Group (TAG). For example, the first TA information could indicate that a TA of (the TRP of) the non-serving cell has the same value of the TA of the Serving Cell. Alternatively, the first TA information could indicate an offset for a TA of (the TRP of) the non-serving cell in respect to the value of the TA of the Serving Cell. The offset could be non-zero (or zero). The first TA information could indicate an identity of the Serving Cell.

Alternatively, the first TA information could indicate that a TA of (the TRP of) the non-serving cell is zero.

In another example, for a UE performing UL transmission or configured with UL resources on a TRP of a Serving Cell, the network could provide or (pre-)configure a first TA information associated with a first TRP of the Serving Cell and a second TA information associated with a second TRP of the Serving Cell.

The second TA information could be associated with a first TA information of the Serving Cell (or a TAG). For example, the first TA information could indicate that the TA of a first TRP of Serving Cell has the same value of the TA of the second TRP. Alternatively, the second TA information could indicate an offset for the second TA of the second TRP in respect to the value of the TA of the first TRP. The offset could be non-zero (or zero). The first TA information could indicate the second TRP (for referencing the TA value).

Alternatively, the first TA information could indicate that a TA of (the TRP of) the Serving Cell is zero.

Additionally and/or alternatively, for a UE configured with a mTRP operation on one or more Cell (e.g., mTRP operation on a single Serving Cell and/or mTRP operation on a Serving Cell and a non-Serving Cell). The network could provide or configure TA information associated with a TRP of the one or more Cell in response to or upon activation of the TRP.

For example, the network could transmit, to the UE, a signaling (e.g., an activation signaling) activating a TRP at least for UL transmission. The signaling could contain a TCI state activation (e.g., MAC CE). The signaling could contain spatial relation info indication or activation (e.g., MAC CE). The network could indicate a TA information associated with the TCI state in the signaling. Additionally and/or alternatively, the network could indicate the TA information associated with the TCI state or with the spatial relation info via a second signaling different from the signaling.

For example, the network could indicate the TA information via a DCI (or via PDCCH). Alternatively, the network could indicate the TA information associated with the TRP via a MAC CE (e.g., Timing Advance Command MAC CE or Absolute Timing Advance Command MAC CE).

NW Determine TA for Second TRP Based on Received SRS and First TRP’s TA

In one example, the network could determine a TA information of a second TRP for the UE based on SRS transmitted to the second TRP by the UE. Additionally and/or alternatively, the network could determine the TA information of the second TRP for the UE based on SRS transmitted to the second TRP by the UE and based on a first TA information associated with a first TRP. The network could obtain/determine the first TA information via random access procedure initiated from the UE to the first TRP. The network may not obtain/determine the TA information of the second TRP for the UE via random access procedure.

For example, the network could provide SRS configuration of a SRS resource (set) (e.g., SRS-config) associated with a second TRP of a Cell for the UE. The SRS resource (set) could indicate periodic and/or slot offset of SRS resource(s). The UE could transmit SRS to the second TRP based on the SRS configuration. The UE could (start to) transmit SRS via the SRS resource(s) in response to receiving the SRS configuration (e.g., periodic SRS transmission). Alternatively, the UE could (start to) transmit SRS via the SRS resource(s) in response to receiving an activation signaling of the SRS configuration (semi-persistent SRS transmission).

The UE could apply the TA information (e.g., Timing Advance N_(TA) and/or offset N_(TA),_(offset)) of the first TRP to SRS transmitted via the SRS resource(s) of the second TRP. Alternatively, the UE could apply no (or zero) TA to SRS transmitted via the SRS resource(s) of the second TRP. Alternatively, the UE could apply a previously configured TA information of the second TRP (e.g., via RRC reconfiguration message) to SRS transmitted via the SRS resource(s).

The UE Could Transmit the SRS via UL Beam(s) Associated with the Second TRP

The network, in response to receiving the SRS, could derive or determine the (relative) timing difference between the first and the second TRP for the UE based on timing of the received SRS. The network could derive (absolute) Timing Advance associated with the second TRP for the UE based on at least the SRS transmission. The network could determine TA information (e.g., Timing Advance N_(TA) and/or offset NT_(A),_(offset) and/or Timing Advance command T_(A)) of the second TRP based on the SRS received. The network could provide/configure the TA information of the second TRP to the UE after receiving the SRS. For example, the network could provide a Timing Advance command to the UE for adjusting UL transmission timing for the second TRP. The UE could apply or use the TA information of the second TRP for transmitting the SRS via the SRS resource(s) of the second TRP after or in response to receiving the TA information of the second TRP (e.g., before activating the second TRP). The UE could apply or use the TA information of the first TRP for transmitting SRS via SRS resource(s) of the first TRP (before and after receiving the TA information of the second TRP).

Alternatively, the UE could apply or use the TA information of the second TRP for transmitting the SRS (and/or transmitting via PUSCH/PUCCH) after activating the second TRP or after activating any of TCI state(s) associated with the second TRP. The UE could apply or use the TA information of the first TRP for transmitting SRS via SRS resource(s) of the first TRP (before and after activating the second TRP and/or TCI state(s) associated with the second TRP). The UE could transmit the SRS (via SRS resource(s) of the first TRP) via UL beam(s) associated with the first TRP.

The second TRP could be associated with a non-Serving Cell (e.g., the UE could perform inter-cell mTRP operation on the first TRP, associated with a serving cell, and the second TRP associated with the non-serving cell). The SRS configuration could be associated with the non-Serving Cell. The UE could start transmitting SRS to the non-Serving Cell in response to receiving the SRS configuration of the non-Serving Cell.

Alternatively, the second TRP could be associated with a Serving Cell. The second TRP could be associated with a same cell as the first TRP.

NW Pre-Configures Second TRP TA, and UE Transmits SRS After Receiving the TA

Alternatively, the network may not provide or derive the TA information of the second TRP based on SRS transmission from the UE to the second TRP. For example, the network could provide or pre-configure the TA information of the second TRP to the UE (e.g., via RRC reconfiguration or via cell configuration). The UE may not apply the TA information of the second TRP upon receiving the configuration. The UE could apply the TA information in response to activation of the second TRP (e.g., activation of UL/DL panel or TCI states or spatial relation info associated with the TRP). The UE could apply the TA information in response to completion of a random access procedure associated with the second TRP or associated with the first TRP.

The TA information of the second TRP could contain a relative value associated with the first TA information of the first TRP. For example, the TA information of the second TRP could contain an (slot) offset relative to the first TA information of the first TRP. The offset set to 0 could indicate that the UE applies the same TA information (e.g., N_(TA) and/or N_(TA),_(offset)) as the first TRP on the second TRP. Additionally and/or alternatively, the TA information of the second TRP could indicate (e.g., via a cell index or bit value) whether the second TRP is synchronous with the first TRP or not. The UE could apply the first TA information of the first TRP (e.g., apply N_(TA) and/or N_(TA),_(offset)) on the second TRP if the TA information of second TRP indicates the second TRP is synchronous with the first TRP.

Additionally and/or alternatively, the TA information of the second TRP could contain an (absolute) value for timing advance or timing adjustment for UE performing UL transmission (e.g., PUCCH, PUSCH, SRS) to the second TRP. The TA information set to 0 could indicate that the UE sets N_(TA) and/or N_(TA),_(offset) to 0 for the second TRP. Additionally and/or alternatively, the TA information of the second TRP could indicate or contains a cell or TRP information (e.g., TCI state/coresetPool index/ SRS resource set/serving cell index/spatial relation info). The UE could set the TA information of the second TRP by applying the same TA information of the cell or the TRP indicated.

Obtain TA via RACH

Additionally and/or alternatively, the network may not provide/configure TA information of the second TRP, e.g., via RRC configuration or via activation signaling of the second TRP. The UE could determine whether to initiate a random access procedure to obtain TA information of a second TRP of a Cell based on at least whether TRP configuration and/or Cell configuration indicates or contains TA information of the second TRP.

The UE could initiate a random access procedure on the second TRP (in order to obtain a TA information) when or if no TA information of the second TRP is provided/configured by the network. Additionally and/or alternatively, the UE could initiate a random access procedure on the second TRP (in order to obtain a TA information) when or if random access resource (e.g., RACH resources) is provided or configured for the second TRP. The UE could initiate the random access procedure when the second TRP is configured/activated. The UE may not initiate a random access procedure to obtain TA information of the second TRP if TA information of the second TRP is provided/configured by the network, e.g., via the TRP configuration and/or Cell configuration.

TRP-Level Based TAG

Additionally and/or alternatively, for a UE performing mTRP operation on a first TRP and a second TRP, the UE could be configured with or provided with a first TAG id associated with the first TRP and a second TAG id associated with the second TRP. The first TRP could be associated with a first TAG and the second TRP could be associated with a second TAG. The UE could be configured with or maintain a first time alignment timer (TAT) for the first TAG, and a second TAT for the second TAG. The first TRP could be associated with a first set of one or more TCI state(s) or beam(s) configured for the UE, and the second TRP could be associated with second set of one or more TCI state(s) or beam(s) configured for the UE. For an example, the UE could be configured with a first (set of) TCI state(s) and a second (set of) TCI state(s) via RRC configuration. The first (set of) TCI state(s) could be associated with a serving cell indicated by a servingcellindex, and the second (set of) TCI state(s) could be associated with a non-serving cell indicated by a PCI or the same serving cell. The first (set of) TCI state(s) could be associated with, or configured with a first TAG id and the second (set of) TCI state(s) could be associated with, or configured with a second TAG id.

Additionally and/or alternatively, the first TRP could be associated with a first set of one or more spatial relation (info) and the second TRP could be associated with a second set of one or more spatial relation (info). For an example, the UE could be configured with a first (set of) spatial relation and a second (set of) spatial relation via RRC configuration. The first (set of) spatial relation could be associated with a serving cell indicated by a servingcellindex, and the second (set of) spatial relation could be associated with a non-serving cell indicated by a PCI or the same serving cell. The first (set of) spatial relation could be associated or configured with a first TAG id and the second (set of) spatial relation could be associated with, or configured with a second TAG id. For each TRP or for each TAG associate with different TRPs, the UE could maintain a Timing Advance between DL and UL (N_(TA)). A network could provide a different Timing Advance command for each TRP (via a Timing Advance command MAC CE).

Cell-Level Based TAG

A non-Serving Cell could be configured with a TAG (different from serving cell’s TAG), or a TAG dedicated for non-Serving Cell(s).

Additionally and/or alternatively, the UE could be configured, by a network (e.g., gNB), with a TAG associated with a non-serving cell. The UE performs inter-cell mTRP operation via DL and/or UL resources of the non-Serving Cell and via DL and/or UL resources of a serving cell. The TAG associated with the non-serving cell could be different from a second TAG associated with the serving cell.

For example, for a UE performing inter-cell mTRP operation on a serving cell and a non-serving cell. The UE could be configured with a first TAG associated with the serving cell (serving cell is in the group of cells associated with the first TAG) and a second TAG associated with the non-serving cell (non-serving cell in a second group of cells associated with the second TAG). The UE could maintain different time alignment timers (e.g., a first TAT) for the first TAG (associated with the serving cell) and the second TAG (associated with the non-serving cell). The UE could maintain different timing advances (e.g., first N_(TA) and second N_(TA)) for the first TAG (associated with the serving cell) and the second TAG (associated with the non-serving cell).

In another example, the UE could be configured with a non-serving cell TAG (dedicated) for one or more non-serving cells. The UE could perform (inter-cell) mTRP operation on the one or more non-serving cells (with one or more serving cells). The TAG may not be associated with a (activated) serving cell. When a time alignment timer associated with the non-serving cell TAG expires, the UE could flush all Hybrid Automatic Repeat Request (HARQ) buffer for all non-serving cells and/or the UE could release PUCCH and/or SRS for all non-serving cells and/or the UE could switch to single TRP operation on serving cells. Each non-serving cell is one individual without a group; or first TRP in an intra-cell belongs to a TAG, but second TRP does not belong to a TAG

Additionally and/or alternatively, the UE could be configured or provided with a TAG associated with the first TRP, and the second TRP may not be associated with or configured with a TAG. The UE could be provided with a time alignment timer for the second TRP. The UE could maintain a (individual) Timing Advance (or N_(TA)). Additionally and/or alternatively, the UE could be provided with an offset (slot or symbol offset or microseconds or one or more time units, e.g., Tc) associated with timing advance of the first TRP. The UE could derive TA of the second TRP based on the offset and the TA of the first TRP.

In another example, non-serving cells of the UE may not be associated with a TAG. Each of the non-serving cells could be configured with or maintain a (individual) time alignment timer. Each of the non-serving cells could maintain an (individual) N_(TA) (or Timing Advance between downlink and uplink). Alternatively, the UE could be provided with an offset (slot or symbol offset or microseconds or one or more time units, e.g., Tc) associated with Timing Advance of a serving cell. The UE could derive TA of the non-serving cell based on the offset and the TA of the serving cell. Two TRPs belong to one TAG, maintaining two N_(TA) or N_(TA) + offset; or serving cell and non-serving cell associated with one TAG, two N_(TA) or N_(TA) + offset

Additionally and/or alternatively, the first TRP and the second TRP could be associated with a same TAG. The UE could maintain a same time alignment timer for both the first TRP and the second TRP. The UE could maintain a first Timing Advance (between DL and UL) for the first TRP and a second Timing Advance for the second TRP (in the TAG). Additionally and/or alternatively, the UE could maintain, or the network could provide a first TA for the first TRP and an offset for the second TRP in the TAG. The offset could be an offset based on the first TA. The UE could derive TA for the non-serving cell based on the first TA and the offset (e.g., TA for the second TRP equals the first TA plus the offset for the second TRP).

Additionally and/or alternatively, the serving cell and the non-serving cell could be associated with a same third TAG.

Additionally and/or alternatively, the serving cell could be associated with a same TAG as the TAG associated with the non-serving cell. The serving cell and the non-serving cell could be associated with a same TAG. The UE could maintain a same time alignment timer for both the serving cell and the non-serving cell. The UE could maintain a first Timing Advance (between DL and UL) for the serving cell and a second Timing Advance for the non-serving cell (in the TAG). Additionally and/or alternatively, the UE could maintain, or the network could provide a first TA for serving cell and an offset for the non-serving cell in the TAG. The offset could be an offset based on the first TA. The UE could derive TA for the non-serving cell based on the first TA and the offset (e.g., TA for the non-serving cell equals the first TA plus the offset for the non-serving cell).

The UE could maintain two TATs, the first TAT and the second TAT, for multi-TRP (mTRP) operation on a first TRP and a second TRP. The first TAT could be associated with the first TRP. The second TAT could be associated with the second TRP. The first TRP and the second TRP could be associated with the same serving cell. Alternatively, the second TRP could be associated with a non-serving cell which is associated with a serving cell of the first TRP.

When or in response to the first TAT expires, the UE could perform one or more of the following actions:

-   Flush all HARQ buffers for the serving cell. -   Release PUCCH for the serving cell. -   Release SRS for the serving cell. -   Clear any configured downlink assignments and configured uplink     grants of the serving cell. -   Clear any PUSCH resource for semi-persistent channel state     information (CSI) reporting for the serving cell. -   Maintain N_(TA) of the first TAG or the third TAG.

Additionally and/or alternatively, the UE could perform one or more of the following actions in response to expiry of the first TAT (while the second TAT is still running and is not expired):

-   (not) Flush all HARQ buffers for the non-serving cell. -   (not) Release PUCCH for the non-serving cell. -   (not) Release SRS for the non-serving cell. -   (not) Clear any configured downlink assignments and configured     uplink grants for the non-serving cell. -   (not) Clear any PUSCH resource for semi-persistent CSI reporting for     the non-serving cell. -   (not) Maintain N_(TA) of the second TAG or the third TAG.

Additionally and/or alternatively, the UE could consider the second TAT to be expired when or in response to the expiry of the first TAT.

When or in response to the second TAT expires, the UE could perform one or more of the following actions:

-   Flush all HARQ buffers for the non-serving cell. -   Release PUCCH for the non-serving cell. -   Release SRS for the non-serving cell. -   Clear any configured downlink assignments and configured uplink     grants for the non-serving cell. -   Clear any PUSCH resource for semi-persistent CSI reporting for the     non-serving cell. -   Maintain N_(TA) of the second TAG.

Additionally and/or alternatively, the UE could perform one or more of the following actions in response to expiry of the second TAT (while the first TAT is still running and is not expired):

-   (not) Flush all HARQ buffers for the serving cell. -   (not) Release PUCCH for the serving cell. -   (not) Release SRS for the serving cell. -   (not) Clear any configured downlink assignments and configured     uplink grants of the serving cell. -   (not) Clear any PUSCH resource for semi-persistent CSI reporting for     the serving cell. -   (not) Maintain N_(TA) of the first TAG.

Additionally and/or alternatively, the UE could consider the first TAT to be expired when or in response to the expiry of the second TAT.

For a UE performing inter-cell mTRP operation between a serving cell and a non-serving cell, when a time alignment timer associated with the non-serving cell expires (and a second time alignment timer associated with the serving cell is not expired), the UE could switch from mTRP operation to single TRP operation on the serving cell.

TAC MAC CE Format

A network could provide time alignment (TA) information for different TRPs (e.g., the first TRP and the second TRP above) of the UE. Each of the different TRPs could be associated with different Timing Advance between DL and UL.

For example, the network (e.g., a gNB) could provide or transmit a MAC CE to the UE for the UE to apply a Timing Advance command. The MAC CE could contain one or more of following field:

-   One or multiple TAG id fields, each indicating id of a TAG. -   One or multiple Non-serving cell id fields, each indicating identity     (e.g., PCI) of a non-serving cell. -   One or multiple Timing Advance Command (TAC) fields, each indicating     a relative or absolute Timing Advance for a TRP. -   One or multiple Offset fields, each indicating a timing offset for     the UE to derive TA for a TRP (based on TA of another TRP).

For example, the network (e.g., a gNB) could provide or transmit a MAC CE to the UE for the UE to apply a TAC for the TRPs associated with the serving cell and/or the non-serving cell (e.g., a (extended) TAC MAC CE). The extended TAC MAC CE could provide TA command for more than one TRPs associated with the UE. The UE could apply different TA command to corresponding TRPs in response to the reception of the MAC CE. An example of an extended TAC MAC CE is shown in FIG. 13 . For a UE performing multi-TRP operation on different TRPs, TRP1 and TRP2 (e.g., via different TCI states or via different spatial relation associated with the TRPs), the network transmits an extended TAC MAC CE for providing TA command to the TRPs. The MAC CE contains or indicates two TAG ids, TAG ID_1 and TAG ID_2. Each of the indicated TAG id is followed by a TA command, which are TAC_TRP1 and TAC_TRP2, respectively. The TRP1 is associated with a TAG with TAG ID_1 and the TRP2 is associated with a TAG with TAG ID_2. Additionally and/or alternatively, the TRP 1 is associated with a cell (e.g., a serving cell or a non-serving cell), wherein the cell is associated with TAG ID_1, and the TRP 2 is associated with a cell (e.g., a same cell as the TRP1’s associated cell or a different cell), wherein the cell is associated with TAG ID_2. The UE applies the TA command TAC_TRP1 to the TRP1 (and/or to the TAG with TAG ID_1) and applies the TA command TAC_TRP2 to the TRP 2 (and/or to the TAG with TAG ID_2) in response to receiving the MAC CE.

TAC Command for Non-Serving Cell

Another example of an extended TAC MAC CE (for non-serving cell) is shown in FIG. 14A. The MAC CE could optionally contain reserved bit (R). The MAC CE could contain a TAG ID. The TAG ID could be associated with at least one non-serving cell. The UE could perform UL transmission via the at least one non-serving cell (e.g., based on inter-cell mTRP operation with a serving cell). Additionally and/or alternatively, the MAC CE could contain an identity indicating or associated with a non-serving cell (e.g., a physical cell id, PCI). The MAC CE could contain a TA command for non-serving cell (TAC_non-serving cell). The TA command could be an absolute value of Timing Advance between DL and UL of the non-serving cell (N_(TA)). Alternatively, the TA command could be a relative value for adjusting current Timing Advance between DL and UL of the non-serving cell. Alternatively, the TA command could indicate a offset between Timing Advance of the at least one non-serving cell and Timing Advance of a serving cell, wherein the UE performs inter-cell operation between the at least one non-serving cell and the serving cell. The UE could apply the TA command to the at least one non-serving cell indicated by the TAG ID or by the non-serving cell ID. Another example is shown in FIG. 14B, where the MAC CE indicates an offset (Offset_TRP2) for a second TRP. The Offset_TRP2 is a timing offset relative to timing advance of a first TRP, TA1. The UE could perform multi-TRP operation between the first and the second TRP. The UE could derive Timing Advance of the second TRP, TA2, based on the Offset1 and the Timing Advance of the first TRP (e.g., TA2 = TA1+Offset_TRP2). The MAC CE could contain second TRP information (e.g., PCI or serving cell index or a TAG ID associated with the second TRP).

One TAG for Both Serving Cell and Non-Serving Cell, and Two TAC / One TAC+ One Offset is Provided

Another example of an extended TAC MAC CE is shown in FIG. 15A. The UE could perform multi-TRP operation with a first TRP and a second TRP. The MAC CE could contain one TAG ID (TAG ID_P). The TAG ID_P could be associated with at least a first TRP (or associated with at least the first TRP and the second TRP). The MAC CE could contain a first TA command for a first TRP (TAC_TRP1). The MAC CE could contain a second TA command for a second TRP (TAC_TRP2). The UE could apply the TAC_TRP1 to the first TRP (e.g., the UE determines which TRP is the first based on smallest TCI state id or spatial relation info id associated with the TRPs). The UE could apply the TAC_TRP2 to the second TRP (e.g., the UE determines which TRP associated to second TAC based on highest TCI state id or spatial relation info id associated with the TRPs). The first and/or the second TA command could be a relative value for adjusting a current Timing Advance for the first and/or the second TRP. Alternatively, the first and/or the second TA command could be an absolute value for the UE to apply or set a Timing Advance on the first and/or the second TRP. The first TRP and the second TRP could be associated with the same serving cell. Alternatively, the second TRP could be associated with at least one non-serving cell, wherein the UE performs inter-cell mTRP operation with the at least one serving cell and the at least one non-serving cell. Alternatively, the MAC CE could contain an offset for the second TRP (Offset_1). The offset could be (UL) timing advance difference between TRP1 and TRP2. The UE could apply the TAC_TRP 1 to the serving cell (or to the cell associated with TRP1) and apply TAC_TRP2 to the non-serving cell (or apply Offset_1 and/or TAC_TRP1 to the non-serving cell).

To derive Timing Advance for the second TRP, TA2, based on the Offset_1, for instance, the UE could add the Offset_1 to a current (or previous) Timing Advance (before applying TAC_TRP1), TA1, of the first TRP (e.g., TA2 = TA1 + Offset_1). For another instance, the UE could add the Offset_1 to a Timing Advance of the first TRP, TA1’, which is derived based on the current (or previous) Timing Advance, TA1, applying the TAC_TRP1 indicated in the TAC MAC CE (e.g., TA2 = TA1 + TAC_TRP1 + Offset_1).

Additionally and/or alternatively, as shown in FIG. 15B, the MAC CE could contain a non-serving cell ID, Non-serving cell id1 (e.g., a PCI of the non-serving cell), and the UE applies the Offset1 or TAC_TRP2 (an absolute TA value or a relative TA value for adjusting current TA) to the non-serving cell associated with Non-serving cell id1.

Additionally and/or alternatively, as shown in FIG. 15C, the MAC CE could contain more than one offsets or TACs for non-serving cells. The MAC CE could indicate TAC_TRP1 (for a serving cell). The MAC CE could indicate two Offsets or TACs for two non-serving cells e.g., (with PCI non-serving cell id1 and id2), and the UE applies the Offset_1, Offset_2 or (TAC_TRP2, TAC_TRP3, absolute TA values or relative TA values for adjusting current TAs)) to the indicated non-serving cells.

Additionally and/or alternatively, as shown in FIG. 15D, the MAC CE could contain more than one offsets or TACs for non-serving cells. The MAC CE may not contain TAG ID field nor contain TA command for serving cells. The MAC CE could indicate two Offsets or TACs for two non-serving cells e.g., (with PCI non-serving cell id1 and id2), and the UE applies the Offset_1, Offset_2 or (TAC_TRP2, TAC_TRP3, absolute TA values or relative TA values for adjusting current TAs)) to the indicated non-serving cells.

Alternatively, the network could provide TA of the first TRP and the second TRP for the UE via a PDCCH signaling (e.g., DCI) instead of a MAC CE.

Any combination of the below concepts, teachings, or embodiments can be jointly combined with the embodiments and disclosure above and herein or formed to a new embodiment.

For a TA information associated with a TRP, the UE could apply the TA information (e.g., derive N_(TA) and/or N_(TA),_(offset)) or derive time difference between UL and DL of the TRP based on or using the TA information.

For a TRP associated with a Cell, the TRP could be indicated or associated with a coresetpool index of the Cell. Additionally and/or alternatively, the TRP could be indicated or could be associated with one or more TCI state(s) or SRS resource set(s) or BFD-RS or spatial relation info which are configured for the Cell. Additionally and/or alternatively, for a TRP associated with a Cell, the TRP could be associated with a physical cell index or serving Cell index of the Cell.

To activate a TRP for a UE, the network could activate TCI state(s) of the UE which is associated with the TRP. To activate the TRP for the UE for UL transmission, the network could activate UL beam(s) or UL TCI state(s) or spatial relation info associated with the TRP (e.g., UL beams for performing PUCCH, PUSCH transmissions).

The first TRP is not synchronous with the second TRP. The first TRP could have a different TA information with the second TRP. The Serving Cell is not synchronous with the non-Serving Cell. The Serving Cell could have a different TA information with the non-Serving Cell. For a UE performing mTRP operation on a first TRP and a second TRP, the UE transmits a transport block (TB) to the first TRP (repetition of) and the same TB to the second TRP. Additionally and/or alternatively, the UE could receive a second TB on the first TRP and the same second TB on the second TRP. The first TRP and the second TRP could be associated with a same Cell (intra-Cell mTRP) or different Cells (inter-Cell mTRP). The UE could perform UL transmissions to one or more TRPs via multiple panels of the UE (e.g., one UL panel corresponds to one TRP for UL transmission). Each of the one or more TRPs could be associated with a Cell. The UE performing mTRP operation could activate more than one TCI states (or spatial relation info) (at the same time), wherein each of the more than one TCI state(s) (or spatial relation info) could be associated with the first TRP or the second TRP. The UE could perform UL or DL communication with the first TRP and the second TRP via the more than one activated TCI states (or spatial relation info).

Each of the more than one TCI states could be associated with a PUSCH or a PUCCH, wherein the UE could perform multiple PUCCH and/or PUSCH transmissions to the first and second TRP via the more than one TCI states (or spatial relation info).

A TRP mentioned above could be replaced by or could be associated with a CORESET Pool (e.g., a coresetPoolIndex) of a Cell. For a UE performing single TRP operation on a Cell, the UE could receive, monitor signaling from the cell via a single CORESET pool. For a UE performing multi-TRP operation on a Cell, the UE could receive, monitor signaling from the cell via more than one CORESET pools.

Additionally and/or alternatively, the TRP mentioned above could be replaced by or could be associated with one or more TCI states of a Cell. For a UE performing single TRP operation on a Cell, the UE could receive or monitor signaling on the cell via one activated TCI state. For a UE performing multi-TRP operation on a Cell, the UE could receive or monitor signaling via more than one activated TCI state(s). Additionally and/or alternatively, the TRP mentioned above could be replaced by or could be associated with an index of a SRS resource.

Additionally and/or alternatively, the TRP mentioned above could be replaced by or could be associated with a SRS resource (set) of a Cell. For a UE performing single TRP operation on a Cell, the UE could transmit SRS on the cell via one SRS resource. For a UE performing multi-TRP operation on a Cell, the UE could transmit SRS via more than one SRS resource(s), wherein each of the more than one SRS resource(s) could be associated with a (different) TRP.

The TCI state(s) or spatial relation info could be associated with or indicate a beam or reference signal (e.g., a Synchronization Signal Block (SSB) or a Channel State Information Reference Signal (CSI-RS)).

Additionally and/or alternatively, the TRP mentioned above could be replace by or could be associated with PUSCH or PUCCH. For a UE performing intra-cell mTRP operation on a Cell, the UE could perform UL transmission via more than one PUSCH associated with the Cell. For a UE performing inter-cell mTRP operation on a Cell, the UE could perform UL transmissions via more than one PUSCH associated with different Cells, wherein the UL transmissions could contain transmitting a same TB on different PUSCHs associated with different Cells.

Additionally and/or alternatively, the TRP mentioned above could be replaced by or could be associated with a set of (UL) beam(s) of a Cell. For a UE performing single TRP operation on a Cell, the UE could perform UL transmission via one set of (UL) beam(s). For a UE performing multi-TRP operation on a Cell, the UE could perform UL transmission via more than one set of (UL) beam(s), wherein each of the more than one set of (UL) beam(s) could be associated with a (different) TRP.

Additionally and/or alternatively, the TRP mentioned above could be replaced by or could be associated with a spatial relation info of a Cell. For a UE performing single TRP operation on a Cell, the UE could activate one spatial relation info (of the Cell). For a UE performing multi-TRP operation on a Cell, the UE could activate more than one spatial relation info (of the Cell), wherein each of the more than one spatial relation info could be associated with a (different) TRP.

A non-serving cell of a UE could be configured with/associated with a PCI value different from PCI values of Serving Cells of the UE. A non-serving Cell could be a neighboring Cell of the UE.

The TA information associated with the second TRP (provided by the network) could contain a (absolute) Timing Advance command (e.g., a T_(A)) or a N_(TA) (e.g., Timing Advance between downlink and uplink) for timing adjustment for UL transmission on the second TRP.

For example, the TA information associated with the second TRP could be a Timing Advance command T_(A) with value range from 0 to 3846, where an amount of the time alignment for the second TRP with subcarrier spacing (SCS) of 2^(µ.)15 kHz is N_(TA) =T_(A) ^(.)16^(.)64/2^(µ). Additionally and/or alternatively, the TA information associated with the second TRP could be a Timing Advance command T_(A) in the form of an index (range from 0 to 63). The UE could adjust a current N_(TA) value to a new NTA value based on the T_(A), wherein for a TRP with SCS of 2^(µ) ^(.)15 kHz, N_(TA_) _(new) ₌ N_(TA) _(old) + (T_(A) -31)^(.)16^(.)64/2^(µ).

Alternatively, the TA information associated with the second TRP could contain N_(TA) associated with the first TRP and/or a (slot) offset associated with the N_(TA) associated with the first TRP. When the (slot) offset equals to 0, the first TRP and the second TRP has the same Timing Advance, or TA, for UL transmission.

Alternatively, the TA information associated with the second TRP could indicate or contain a cell index of the second TRP or indicate the second TRP. The UE could apply the TA information to the second TRP.

The TA information could be UL TA information containing Timing Advance between downlink and uplink (e.g., a N_(TA)) and/or a fixed offset used to calculate the Timing Advance (e.g., a N_(TA),_(offset)).

The activation signaling of a TRP could be a TCI state activation/deactivation MAC CE or spatial relation info activation/deactivation MAC CE.

The activation signaling of a TRP could be a DCI indicating activation/deactivation of a TCI state. The DCI may not contain nor indicate a UL grant or a DL assignment (e.g., a beam indication DCI). The activation signaling of a TRP could be a DCI or MAC CE indicating activation/deactivation of spatial relation info.

The PDCCH signaling could be a (new format of) PDCCH order. The PDCCH signaling could indicate a Cell id (e.g., PCI) and/or a beam (e.g., TCI state id) and/or TRP id (e.g., BFD-RS set(s) id) for the (first and/or second) TRP. In response to completion of the random access procedure on the non-Serving Cell, the UE could perform SRS transmission on the Cell. The UE may not perform SRS transmission (even if SRS resource is configured for the non-Serving Cell) before obtaining TA information of the non-Serving Cell.

The first TRP is not synchronous with the second TRP. The first TRP could have a different TA information with the second TRP. The Serving Cell is not synchronous with the non-Serving Cell. The Serving Cell could have a different TA information with the non-Serving Cell.

The TCI states activation MAC CE could be TCI State Indication for UE-specific PDCCH MAC CE.

The TCI states activation MAC CE could be TCI States Activation/Deactivation for UE-specific PDSCH MAC CE.

The First TRP and the Second TRP May Not be in the Same TAG

The PDCCH signaling could be a PDCCH order. The PDCCH signaling could be a DCI format different from a PDCCH order.

The random access procedure could be a contention-based or contention-free random access procedure.

For a TA information associated with a TRP, a UE could maintain a timer for the TA information. The TA information is considered valid when the timer is running. The TA information is considered invalid when the timer expires or is not running. The UE could (re)start the timer of a TA information of a TRP (and does not restart timer of TA information of other TRPs) if or when receiving a Timing Advance command (via a MAC CE) of the TA information of the TRP.

Any combination of above concepts can be jointly combined or formed to a new embodiment. The following embodiments can be used to solve at least (but not limited to) the issue mentioned above.

Referring to FIG. 16 , with this and other concepts, systems, and methods of the present invention, a method 1000 for a UE in a wireless communication system comprises receiving, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP (step 1002), initiating a first random access procedure on the first TRP, wherein the UE obtains a first TA information of the first TRP in the random access procedure (step 1004), receiving, from the network, a signaling indicating activation for UL communication of the second TRP (step 1006), initiating a second random access procedure on the second TRP in response to the signaling, wherein the UE obtains a second TA information of the second TRP in the second random access procedure (step 1008), and transmitting a TB on the first TRP by applying the first TA information and transmitting the TB on the second TRP by applying the second TA information (step 1010).

In various embodiments, the UE is configured with multi-TRP operation on the first TRP and the second TRP.

In various embodiments, the first TRP is associated with a serving cell.

In various embodiments, the second TRP is associated with a serving cell same as the first TRP.

In various embodiments, the second TRP is associated with a non-Serving Cell.

In various embodiments, the UE does not consider the non-Serving Cell to be a Serving Cell in response to completion of the second random access procedure.

In various embodiments, the first and/or second TA information is a Timing Advance command for the first and/or second TRP.

In various embodiments, the first and/or second TA information is a time alignment, or a Timing Advance (N_(TA)) between downlink and uplink of the first and/or second TRP.

In various embodiments, the UE does not perform the second random access procedure to the second TRP when or if a TA information associated with the second TRP has been provided by the network in the configuration.

In various embodiments, the UE does not perform the second random access procedure to the second TRP when or if the TA information associated with the second TRP has been provided by the network in the signaling or before receiving the signaling.

In various embodiments, the UE initiates the first random access procedure in response to a PDCCH order from the network.

In various embodiments, the UE initiates the first random access procedure in response to connection establishment triggered by the UE.

In various embodiments, the signaling is an activation MAC CE activating TCI state(s) associated with the second TRP.

In various embodiments, the signaling is a PDCCH signaling indicating mTRP operation.

In various embodiments, the signaling indicates or provides a PCI.

In various embodiments, the signaling indicates a serving cell index.

In various embodiments, the signaling indicates one or more TCI state(s) (e.g., TCI state(s) ID).

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) receive, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP, (ii) initiate a first random access procedure on the first TRP, wherein the UE obtains a first TA information of the first TRP in the random access procedure, (iii) receive, from the network, a signaling indicating activation for UL communication of the second TRP, (iv) initiate a second random access procedure on the second TRP in response to the signaling, wherein the UE obtains a second TA information of the second TRP in the second random access procedure, and (v) transmit a TB on the first TRP by applying the first TA information and transmitting the TB on the second TRP by applying the second TA information. Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to FIG. 17 , with this and other concepts, systems, and methods of the present invention, a method 1020 for a UE in a wireless communication system comprises performing UL transmission on a first TRP and a second TRP (step 1022), receiving, from a network, a signaling containing a first TA information and a second TA information (step 1024), and applying a first TA information on the first TRP and the second TA information on the second TRP (step 1026).

In various embodiments, the first TRP and the second TRP are in different Timing Advance Group (TAG).

In various embodiments, the first TRP and the second TRP are in the same TAG.

In various embodiments, the first and/or second TA information is a Timing Advance command for the first and/or second TRP.

In various embodiments, the first and/or second TA information is a time alignment, or a Timing Advance (N_(TA)) between downlink and uplink of the first and/or second TRP.

In various embodiments, the second TA information is an offset between Timing Advance of the first TRP and the Timing Advance of the second TRP.

In various embodiments, the first TRP is associated with a serving cell.

In various embodiments, the second TRP is associated with a serving cell same as the first TRP.

In various embodiments, the second TRP is associated with a non-Serving Cell and the first TRP is associated with a Serving Cell.

In various embodiments, the UE performs inter-cell mTRP operation on the non-serving cell and the serving cell.

In various embodiments, the signaling is a MAC CE.

In various embodiments, the signaling contains a physical cell id associated with the second TRP.

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) perform UL transmission on a first TRP and a second TRP, (ii) receive, from a network, a signaling containing a first time alignment TA information and a second TA information, and (iii) apply a first TA information on the first TRP and the second TA information on the second TRP (step 1024). Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to FIG. 18 , with this and other concepts, systems, and methods of the present invention, a method 1030 for a UE in a wireless communication system comprises performing inter-cell mTRP operation on a serving cell and a non-serving cell, wherein the UE maintains a first TA timer for the serving cell and a second TA timer on the non-serving cell (step 1032), and in response to expiry of the first TA timer, flush HARQ buffers of the non-serving cell (step 1034).

In various embodiments, the second TA timer is not expired when the first TA timer expired.

In various embodiments, the UE does not consider the second TA timer expired when the first TA timer expired.

In various embodiments, the UE flushes HARQ buffers of the serving cell and the non-serving cell in response to expiry of the first TA timer.

In various embodiments, the UE relases PUCCH for the non-serving cell in response to expiry of the first TA timer.

In various embodiments, the UE clears PUSCH resource for CSI reporting for the non-serving cell in response to expiry of the first TA timer.

In various embodiments, the UE clears configured DL assignments and UL grants for the non-serving cell in response to expiry of the first TA timer.

In various embodiments, the serving cell and the non-serving cell are in different TAGs.

In various embodiments, the serving cell and the non-serving cell are in the same TAG.

In various embodiments, the UE maintain a first N_(TA) for the serving cell and a second N_(TA) for the non-serving cell.

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) perform inter-cell mTRP operation on a serving cell and a non-serving cell, wherein the UE maintains a first TA timer for the serving cell and a second TA timer on the non-serving cell, and (ii) in response to expiry of the first TA timer, flush HARQ buffers of the non-serving cell. Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to FIG. 19 , with this and other concepts, systems, and methods of the present invention, a method 1040 for a network in a wireless communication system comprises configuring a UE with UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP (step 1042), receiving a SRS from a UE at a timing on a second TRP (step 1044), determining a Timing Advance command associated with the second TRP for the UE based on at least the timing receiving the SRS (step 1046), and transmitting a signaling to a UE, wherein the signaling includes or indicates the time alignment information associated with the second TRP (step 1048).

In various embodiments, the network determines the Timing Advance command further based on time alignment information associated with a first TRP.

In various embodiments, the UE transmits the SRS at the timing based on a time alignment associated with the first TRP.

In various embodiments, the time alignment information associated with the second TRP is an offset associated with time alignment associated with the first TRP.

In various embodiments, a time alignment associated with the second TRP of the UE is the time alignment associated with the first TRP plus or minus the offset.

In various embodiments, the signaling contains an activation of the second TRP, wherein the UE activates UL transmission via the second TRP in response to the signaling.

In various embodiments, the time alignment information associated with the second TRP is a Timing Advance command for the second TRP.

In various embodiments, the time alignment information associated with the second TRP is a time alignment, or a Timing Advance (N_(TA)) between downlink and uplink of the second TRP.

In various embodiments, the UE performs multi-TRP operation on the first TRP and the second TRP.

In various embodiments, the first TRP and the second TRP are associated with different Cells.

In various embodiments, the first TRP and the second TRP are associated with a same Cell.

In various embodiments, the UE obtains time alignment associated with the first TRP via a random access procedure.

In various embodiments, the UE does not obtain the time alignment associated with the second TRP via a random access procedure.

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a network, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) configure a UE with UL resource(s) associated with a first TRP and UL resource(s) associated with a second TRP, (ii) receive a SRS from a UE at a timing on a second TRP, (iii) determine a Timing Advance command associated with the second TRP for the UE based on at least the timing receiving the SRS, and (iv) transmit a signaling to a UE, wherein the signaling includes or indicates the time alignment information associated with the second TRP. Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to FIG. 20 , with this and other concepts, systems, and methods of the present invention, a method 1050 for a UE in a wireless communication system comprises receiving, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated a second TRP (step 1052), receiving, from the network, a signaling indicating an activation of the second TRP (step 1054), and determining whether to perform a random access procedure to the second TRP in response to the signaling based on at least a time alignment information associated with the second TRP has been provided by the network (step 1056).

In various embodiments, the UE does not perform a random access procedure to the second TRP when or if a time alignment information associated with the second TRP has been provided by the network (in the signaling).

In various embodiments, the UE does not perform a random access procedure to the second TRP when or if the time alignment information associated with the second TRP has been provided by the network in the signaling.

In various embodiments, the UE does not perform a random access procedure to the second TRP when or if the time alignment information associated with the second TRP has been provided by the network via a previous signaling before the signaling.

In various embodiments, the UE does not perform a random access procedure to the second TRP when or if the time alignment information associated with the second TRP has been provided by the network in the configuration.

In various embodiments, the UE performs a random access procedure to the second TRP when or if a time alignment information associated with the second TRP has not been provided by the network.

In various embodiments, the UE determines whether to perform a random access procedure to the second TRP further based on whether random access resources is provided (via the configuration) for the second TRP.

In various embodiments, the UE performs a random access procedure to the second TRP when or if random access resources is provided (via the configuration) for the second TRP.

In various embodiments, the UE does not perform a random access procedure to the second TRP when or if random access resources is not provided (via the configuration) for the second TRP.

In various embodiments, the UE performs multi-TRP operation on the first TRP and the second TRP.

In various embodiments, the first TRP and the second TRP are associated with different Cells.

In various embodiments, the first TRP and the second TRP are associated with a same Cell.

In various embodiments, the time alignment information associated with the second TRP is a Timing Advance command for the second TRP.

In various embodiments, the time alignment information associated with the second TRP is a time alignment, or a Timing Advance (N_(TA)) between downlink and uplink of the second TRP.

In various embodiments, the time alignment information associated with the second TRP is an offset associated with time alignment associated with the first TRP.

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) receive, from a network, a configuration configuring UL resource(s) associated with a first TRP and UL resource(s) associated a second TRP, (ii) receive, from the network, a signaling indicating an activation of the second TRP, and (iii) determine whether to perform a random access procedure to the second TRP in response to the signaling based on at least a time alignment information associated with the second TRP has been provided by the network. Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to FIG. 21 , with this and other concepts, systems, and methods of the present invention, a method 1060 for a UE in a wireless communication system comprises receiving a signaling, wherein the signaling indicates activation for a first TRP and/or is a PDCCH signal (step 1062), determining to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first TA information associated with the first TRP (step 1064), and performing multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information (step 1066).

In various embodiments, the method further comprises determining to not perform the first random access procedure if the time alignment timer associated with the first TRP is running.

In various embodiments, the method further comprises obtaining the second TA information in a second random access procedure on the second TRP.

In various embodiments, the first TRP and the second TRP are associated with different TAGs.

In various embodiments, the activation for the first TRP is to activate a TCI state or a spatial relation info associated with the first TRP.

In various embodiments, the first TRP and the second TRP are TRPs of a same serving cell of the UE.

In various embodiments, the second TRP is a TRP of a serving cell of the UE and the first TRP is associated with a PCI different from PCI values of serving cells of the UE.

In various embodiments, the first TA information is a Timing Advance between downlink and uplink of the first TRP and the second TA information is a Timing Advance between downlink and uplink of the second TRP.

In various embodiments, the signaling indicates or provides information of a PCI and/or a coresetpool index and/or a BFD-RS set associated with the first TRP.

In various embodiments, the signaling indicates one or more TCI states and/or one or more SRS resource set identities and/or one or more spatial relation info associated with the first TRP.

In various embodiments, the signaling indicates whether to obtain the first TA information associated with the first TRP.

In various embodiments, the signaling indicates whether to perform the first random access procedure.

In various embodiments, the method further comprises performing UL transmission on the first TRP by applying the first TA information and performing UL transmission on the second TRP by applying the second TA information.

In various embodiments, the first random access procedure is contention-free or contention-based.

Referring back to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the device 300 includes a program code 312 stored in memory 310 of the transmitter. The CPU 308 could execute program code 312 to: (i) receive a signaling, wherein the signaling indicates activation for a first TRP and/or is a PDCCH signal, (ii) determine to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first TA information associated with the first TRP, and (iii) perform multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information. Moreover, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Any combination of the above concepts or teachings can be jointly combined or formed to a new embodiment. The disclosed details and embodiments can be used to solve at least (but not limited to) the issues mentioned above and herein.

It is noted that any of the methods, alternatives, steps, examples, and embodiments proposed herein may be applied independently, individually, and/or with multiple methods, alternatives, steps, examples, and embodiments combined together.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects, concurrent channels may be established based on pulse repetition frequencies. In some aspects, concurrent channels may be established based on pulse position or offsets. In some aspects, concurrent channels may be established based on time hopping sequences. In some aspects, concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of ordinary skill in the art would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Moreover, in some aspects, any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects, a computer program product may comprise packaging materials.

While the invention has been described in connection with various aspects and examples, it will be understood that the invention is capable of further modifications. This application is intended to cover any variations, uses or adaptation of the invention following, in general, the principles of the invention, and including such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains. 

What is claimed is:
 1. A method of a User Equipment (UE), comprising: receiving a signaling, wherein the signaling indicates activation for a first Transmission/Reception Point (TRP) and/or is a Physical Downlink Control Channel (PDCCH) signal; determining to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first Time Alignment (TA) information associated with the first TRP; and performing multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information.
 2. The method of claim 1, further comprising determining to not perform the first random access procedure if a time alignment timer associated with the first TRP is running.
 3. The method of claim 1, further comprising obtaining the second TA information in a second random access procedure on the second TRP.
 4. The method of claim 1, wherein the first TRP and the second TRP are associated with different Timing Advance Groups (TAGs).
 5. The method of claim 1, wherein the activation for the first TRP is to activate a Transmission Configuration Indicator (TCI) state or a spatial relation info associated with the first TRP.
 6. The method of claim 1, wherein the first TRP and the second TRP are TRPs of a same serving cell of the UE, or the second TRP is a TRP of a serving cell of the UE and the first TRP is associated with a Physical Cell Identity (PCI) different from PCI values of serving cells of the UE.
 7. The method of claim 1, wherein the first TA information is a Timing Advance between downlink and uplink of the first TRP and the second TA information is a Timing Advance between downlink and uplink of the second TRP.
 8. The method of claim 1, wherein the signaling indicates or provides information of a PCI and/or a coresetpool index and/or a beam failure detection reference signal (BFD-RS) set associated with the first TRP.
 9. The method of claim 1, wherein the signaling indicates one or more TCI states and/or one or more Sounding Reference Signal (SRS) resource set identities and/or one or more spatial relation info associated with the first TRP.
 10. The method of claim 1, wherein the signaling indicates whether to obtain the first TA information associated with the first TRP or indicates whether to perform the first random access procedure.
 11. The method of claim 1, further comprising performing UL transmission on the first TRP by applying the first TA information and performing UL transmission on the second TRP by applying the second TA information.
 12. The method of claim 1, wherein the first random access procedure is contention-free or contention-based.
 13. A User Equipment (UE), comprising: a memory; and a processor operatively connected to the memory, wherein the processor is configured to execute a program code to: receive a signaling, wherein the signaling indicates activation for a first Transmission/Reception Point (TRP) and/or is a Physical Downlink Control Channel (PDCCH) signal; determine to perform a first random access procedure on the first TRP, based on the signaling, to obtain a first Time Alignment (TA) information associated with the first TRP; and perform multi-TRP operation on the first TRP associated with the first TA information and a second TRP associated with a second TA information.
 14. The UE of claim 13, wherein the processor is further configured to execute the program code to determine to not perform the first random access procedure if a time alignment timer associated with the first TRP is running.
 15. The UE of claim 13, wherein the first TRP and the second TRP are associated with different Timing Advance Groups (TAGs).
 16. The UE of claim 13, wherein the activation for the first TRP is to activate a Transmission Configuration Indicator (TCI) state or a spatial relation info associated with the first TRP.
 17. The UE of claim 13, wherein the first TRP and the second TRP are TRPs of a same serving cell of the UE, or the second TRP is a TRP of a serving cell of the UE and the first TRP is associated with a Physical Cell Identity (PCI) different from PCI values of serving cells of the UE.
 18. The UE of claim 13, wherein the signaling indicates or provides information of a PCI and/or a coresetpool index and/or a beam failure detection reference signal (BFD-RS) set associated with the first TRP.
 19. The UE of claim 13, wherein the signaling indicates one or more TCI states and/or one or more Sounding Reference Signal (SRS) resource set identities and/or one or more spatial relation info associated with the first TRP.
 20. The UE of claim 13, wherein the signaling indicates whether to obtain the first TA information associated with the first TRP or indicates whether to perform the first random access procedure. 